QuayAccessToken generates Quay oauth token for pulling/pushing images
4 top-level fields · last changed in External Secrets Operator v2.10.0
APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources
Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds
QuayAccessTokenSpec defines the desired state to generate a Quay access token.
Name of the robot account you are federating with
Name of the service account you are federating with
Audience specifies the `aud` claim for the service account token Some providers automatically extend the audience field based on well-known annotations for workload identity (e.g. IRSA or GCP Workload Identity)
The name of the ServiceAccount resource being referred to.
Namespace of the resource being referred to. Ignored if referent is not cluster-scoped, otherwise defaults to the namespace of the referent.
URL configures the Quay instance URL. Defaults to quay.io.
Source: bundle.yaml
Changes to QuayAccessToken (generators.external-secrets.io/v1alpha1) in each External Secrets Operator version, compared to the version before it.
1 property has changed the description
Released · View QuayAccessToken in v2.10.0
1 property has changed the description
Released · View QuayAccessToken in v0.20.4
QuayAccessToken was first seen on this version of External Secrets Operator
Released · View QuayAccessToken in v0.13.0
No examples of QuayAccessToken yet. Contribute one on GitHub.
kubespec.dev