fluxcd
/
source-controller
mirror of https://github.com/fluxcd/source-controller.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Update controller-gen to v0.16.1 

Signed-off-by: Stefan Prodan <stefan.prodan@gmail.com>
This commit is contained in:
Stefan Prodan 2024-08-23 13:42:28 +03:00
parent 5be0c53729
commit cd48373d6c
No known key found for this signature in database
GPG Key ID: 3299AEB0E4085BAF
7 changed files with 58 additions and 360 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
Makefile
View File

@ -38,7 +38,7 @@ FUZZ_TIME ?= 1m
GO_STATIC_FLAGS=-ldflags "-s -w" -tags 'netgo,osusergo,static_build$(addprefix ,,$(GO_TAGS))' GO_STATIC_FLAGS=-ldflags "-s -w" -tags 'netgo,osusergo,static_build$(addprefix ,,$(GO_TAGS))'
# API (doc) generation utilities # API (doc) generation utilities
CONTROLLER_GEN_VERSION ?= v0.15.0 CONTROLLER_GEN_VERSION ?= v0.16.1
GEN_API_REF_DOCS_VERSION ?= e327d0730470cbd61b06300f81c5fcf91c23c113 GEN_API_REF_DOCS_VERSION ?= e327d0730470cbd61b06300f81c5fcf91c23c113
# If gobin not set, create one on ./build and add to path. # If gobin not set, create one on ./build and add to path.

74
config/crd/bases/source.toolkit.fluxcd.io_buckets.yaml
View File

@ -3,7 +3,7 @@ apiVersion: apiextensions.k8s.io/v1
kind: CustomResourceDefinition kind: CustomResourceDefinition
metadata: metadata:
annotations: annotations:
controller-gen.kubebuilder.io/version: v0.15.0 controller-gen.kubebuilder.io/version: v0.16.1
name: buckets.source.toolkit.fluxcd.io name: buckets.source.toolkit.fluxcd.io
spec: spec:
group: source.toolkit.fluxcd.io group: source.toolkit.fluxcd.io
@ -90,19 +90,16 @@ spec:
CertSecretRef can be given the name of a Secret containing CertSecretRef can be given the name of a Secret containing
either or both of either or both of
- a PEM-encoded client certificate (`tls.crt`) and private - a PEM-encoded client certificate (`tls.crt`) and private
key (`tls.key`); key (`tls.key`);
- a PEM-encoded CA certificate (`ca.crt`) - a PEM-encoded CA certificate (`ca.crt`)
and whichever are supplied, will be used for connecting to the and whichever are supplied, will be used for connecting to the
bucket. The client cert and key are useful if you are bucket. The client cert and key are useful if you are
authenticating with a certificate; the CA cert is useful if authenticating with a certificate; the CA cert is useful if
you are using a self-signed server certificate. The Secret must you are using a self-signed server certificate. The Secret must
be of type `Opaque` or `kubernetes.io/tls`. be of type `Opaque` or `kubernetes.io/tls`.
This field is only supported for the `generic` provider. This field is only supported for the `generic` provider.
properties: properties:
name: name:
@ -179,7 +176,6 @@ spec:
Service for fetching temporary credentials to authenticate in a Service for fetching temporary credentials to authenticate in a
Bucket provider. Bucket provider.
This field is only supported for the `aws` and `generic` providers. This field is only supported for the `aws` and `generic` providers.
properties: properties:
certSecretRef: certSecretRef:
@ -187,19 +183,16 @@ spec:
CertSecretRef can be given the name of a Secret containing CertSecretRef can be given the name of a Secret containing
either or both of either or both of
- a PEM-encoded client certificate (`tls.crt`) and private - a PEM-encoded client certificate (`tls.crt`) and private
key (`tls.key`); key (`tls.key`);
- a PEM-encoded CA certificate (`ca.crt`) - a PEM-encoded CA certificate (`ca.crt`)
and whichever are supplied, will be used for connecting to the and whichever are supplied, will be used for connecting to the
STS endpoint. The client cert and key are useful if you are STS endpoint. The client cert and key are useful if you are
authenticating with a certificate; the CA cert is useful if authenticating with a certificate; the CA cert is useful if
you are using a self-signed server certificate. The Secret must you are using a self-signed server certificate. The Secret must
be of type `Opaque` or `kubernetes.io/tls`. be of type `Opaque` or `kubernetes.io/tls`.
This field is only supported for the `ldap` provider. This field is only supported for the `ldap` provider.
properties: properties:
name: name:
@ -320,16 +313,8 @@ spec:
conditions: conditions:
description: Conditions holds the conditions for the Bucket. description: Conditions holds the conditions for the Bucket.
items: items:
description: "Condition contains details for one aspect of the current description: Condition contains details for one aspect of the current
state of this API Resource.\n---\nThis struct is intended for state of this API Resource.
direct use as an array at the field path .status.conditions. For
example,\n\n\n\ttype FooStatus struct{\n\t // Represents the
observations of a foo's current state.\n\t // Known .status.conditions.type
are: \"Available\", \"Progressing\", and \"Degraded\"\n\t //
+patchMergeKey=type\n\t // +patchStrategy=merge\n\t // +listType=map\n\t
\ // +listMapKey=type\n\t Conditions []metav1.Condition `json:\"conditions,omitempty\"
patchStrategy:\"merge\" patchMergeKey:\"type\" protobuf:\"bytes,1,rep,name=conditions\"`\n\n\n\t
\ // other fields\n\t}"
properties: properties:
lastTransitionTime: lastTransitionTime:
description: |- description: |-
@ -370,12 +355,7 @@ spec:
- Unknown - Unknown
type: string type: string
type: type:
description: |- description: type of condition in CamelCase or in foo.example.com/CamelCase.
type of condition in CamelCase or in foo.example.com/CamelCase.
---
Many .condition.type values are consistent across resources like Available, but because arbitrary conditions can be
useful (see .node.status.conditions), the ability to deconflict is important.
The regex it matches is (dns1123SubdomainFmt/)?(qualifiedNameFmt)
maxLength: 316 maxLength: 316
pattern: ^([a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*/)?(([A-Za-z0-9][-A-Za-z0-9_.]*)?[A-Za-z0-9])$ pattern: ^([a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*/)?(([A-Za-z0-9][-A-Za-z0-9_.]*)?[A-Za-z0-9])$
type: string type: string
@ -566,22 +546,15 @@ spec:
description: URL is the HTTP address of this artifact. description: URL is the HTTP address of this artifact.
type: string type: string
required: required:
- lastUpdateTime
- path - path
- url - url
type: object type: object
conditions: conditions:
description: Conditions holds the conditions for the Bucket. description: Conditions holds the conditions for the Bucket.
items: items:
description: "Condition contains details for one aspect of the current description: Condition contains details for one aspect of the current
state of this API Resource.\n---\nThis struct is intended for state of this API Resource.
direct use as an array at the field path .status.conditions. For
example,\n\n\n\ttype FooStatus struct{\n\t // Represents the
observations of a foo's current state.\n\t // Known .status.conditions.type
are: \"Available\", \"Progressing\", and \"Degraded\"\n\t //
+patchMergeKey=type\n\t // +patchStrategy=merge\n\t // +listType=map\n\t
\ // +listMapKey=type\n\t Conditions []metav1.Condition `json:\"conditions,omitempty\"
patchStrategy:\"merge\" patchMergeKey:\"type\" protobuf:\"bytes,1,rep,name=conditions\"`\n\n\n\t
\ // other fields\n\t}"
properties: properties:
lastTransitionTime: lastTransitionTime:
description: |- description: |-
@ -622,12 +595,7 @@ spec:
- Unknown - Unknown
type: string type: string
type: type:
description: |- description: type of condition in CamelCase or in foo.example.com/CamelCase.
type of condition in CamelCase or in foo.example.com/CamelCase.
---
Many .condition.type values are consistent across resources like Available, but because arbitrary conditions can be
useful (see .node.status.conditions), the ability to deconflict is important.
The regex it matches is (dns1123SubdomainFmt/)?(qualifiedNameFmt)
maxLength: 316 maxLength: 316
pattern: ^([a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*/)?(([A-Za-z0-9][-A-Za-z0-9_.]*)?[A-Za-z0-9])$ pattern: ^([a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*/)?(([A-Za-z0-9][-A-Za-z0-9_.]*)?[A-Za-z0-9])$
type: string type: string
@ -737,19 +705,16 @@ spec:
CertSecretRef can be given the name of a Secret containing CertSecretRef can be given the name of a Secret containing
either or both of either or both of
- a PEM-encoded client certificate (`tls.crt`) and private - a PEM-encoded client certificate (`tls.crt`) and private
key (`tls.key`); key (`tls.key`);
- a PEM-encoded CA certificate (`ca.crt`) - a PEM-encoded CA certificate (`ca.crt`)
and whichever are supplied, will be used for connecting to the and whichever are supplied, will be used for connecting to the
bucket. The client cert and key are useful if you are bucket. The client cert and key are useful if you are
authenticating with a certificate; the CA cert is useful if authenticating with a certificate; the CA cert is useful if
you are using a self-signed server certificate. The Secret must you are using a self-signed server certificate. The Secret must
be of type `Opaque` or `kubernetes.io/tls`. be of type `Opaque` or `kubernetes.io/tls`.
This field is only supported for the `generic` provider. This field is only supported for the `generic` provider.
properties: properties:
name: name:
@ -826,7 +791,6 @@ spec:
Service for fetching temporary credentials to authenticate in a Service for fetching temporary credentials to authenticate in a
Bucket provider. Bucket provider.
This field is only supported for the `aws` and `generic` providers. This field is only supported for the `aws` and `generic` providers.
properties: properties:
certSecretRef: certSecretRef:
@ -834,19 +798,16 @@ spec:
CertSecretRef can be given the name of a Secret containing CertSecretRef can be given the name of a Secret containing
either or both of either or both of
- a PEM-encoded client certificate (`tls.crt`) and private - a PEM-encoded client certificate (`tls.crt`) and private
key (`tls.key`); key (`tls.key`);
- a PEM-encoded CA certificate (`ca.crt`) - a PEM-encoded CA certificate (`ca.crt`)
and whichever are supplied, will be used for connecting to the and whichever are supplied, will be used for connecting to the
STS endpoint. The client cert and key are useful if you are STS endpoint. The client cert and key are useful if you are
authenticating with a certificate; the CA cert is useful if authenticating with a certificate; the CA cert is useful if
you are using a self-signed server certificate. The Secret must you are using a self-signed server certificate. The Secret must
be of type `Opaque` or `kubernetes.io/tls`. be of type `Opaque` or `kubernetes.io/tls`.
This field is only supported for the `ldap` provider. This field is only supported for the `ldap` provider.
properties: properties:
name: name:
@ -967,16 +928,8 @@ spec:
conditions: conditions:
description: Conditions holds the conditions for the Bucket. description: Conditions holds the conditions for the Bucket.
items: items:
description: "Condition contains details for one aspect of the current description: Condition contains details for one aspect of the current
state of this API Resource.\n---\nThis struct is intended for state of this API Resource.
direct use as an array at the field path .status.conditions. For
example,\n\n\n\ttype FooStatus struct{\n\t // Represents the
observations of a foo's current state.\n\t // Known .status.conditions.type
are: \"Available\", \"Progressing\", and \"Degraded\"\n\t //
+patchMergeKey=type\n\t // +patchStrategy=merge\n\t // +listType=map\n\t
\ // +listMapKey=type\n\t Conditions []metav1.Condition `json:\"conditions,omitempty\"
patchStrategy:\"merge\" patchMergeKey:\"type\" protobuf:\"bytes,1,rep,name=conditions\"`\n\n\n\t
\ // other fields\n\t}"
properties: properties:
lastTransitionTime: lastTransitionTime:
description: |- description: |-
@ -1017,12 +970,7 @@ spec:
- Unknown - Unknown
type: string type: string
type: type:
description: |- description: type of condition in CamelCase or in foo.example.com/CamelCase.
type of condition in CamelCase or in foo.example.com/CamelCase.
---
Many .condition.type values are consistent across resources like Available, but because arbitrary conditions can be
useful (see .node.status.conditions), the ability to deconflict is important.
The regex it matches is (dns1123SubdomainFmt/)?(qualifiedNameFmt)
maxLength: 316 maxLength: 316
pattern: ^([a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*/)?(([A-Za-z0-9][-A-Za-z0-9_.]*)?[A-Za-z0-9])$ pattern: ^([a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*/)?(([A-Za-z0-9][-A-Za-z0-9_.]*)?[A-Za-z0-9])$
type: string type: string

67
config/crd/bases/source.toolkit.fluxcd.io_gitrepositories.yaml
View File

@ -3,7 +3,7 @@ apiVersion: apiextensions.k8s.io/v1
kind: CustomResourceDefinition kind: CustomResourceDefinition
metadata: metadata:
annotations: annotations:
controller-gen.kubebuilder.io/version: v0.15.0 controller-gen.kubebuilder.io/version: v0.16.1
name: gitrepositories.source.toolkit.fluxcd.io name: gitrepositories.source.toolkit.fluxcd.io
spec: spec:
group: source.toolkit.fluxcd.io group: source.toolkit.fluxcd.io
@ -132,7 +132,6 @@ spec:
description: |- description: |-
Commit SHA to check out, takes precedence over all reference fields. Commit SHA to check out, takes precedence over all reference fields.
This can be combined with Branch to shallow clone the branch, in which This can be combined with Branch to shallow clone the branch, in which
the commit is expected to exist. the commit is expected to exist.
type: string type: string
@ -140,7 +139,6 @@ spec:
description: |- description: |-
Name of the reference to check out; takes precedence over Branch, Tag and SemVer. Name of the reference to check out; takes precedence over Branch, Tag and SemVer.
It must be a valid Git reference: https://git-scm.com/docs/git-check-ref-format#_description It must be a valid Git reference: https://git-scm.com/docs/git-check-ref-format#_description
Examples: "refs/heads/main", "refs/tags/v0.1.0", "refs/pull/420/head", "refs/merge-requests/1/head" Examples: "refs/heads/main", "refs/tags/v0.1.0", "refs/pull/420/head", "refs/merge-requests/1/head"
type: string type: string
@ -193,7 +191,6 @@ spec:
description: |- description: |-
Mode specifies which Git object(s) should be verified. Mode specifies which Git object(s) should be verified.
The variants "head" and "HEAD" both imply the same thing, i.e. verify The variants "head" and "HEAD" both imply the same thing, i.e. verify
the commit that the HEAD of the Git repository points to. The variant the commit that the HEAD of the Git repository points to. The variant
"head" solely exists to ensure backwards compatibility. "head" solely exists to ensure backwards compatibility.
@ -275,16 +272,8 @@ spec:
conditions: conditions:
description: Conditions holds the conditions for the GitRepository. description: Conditions holds the conditions for the GitRepository.
items: items:
description: "Condition contains details for one aspect of the current description: Condition contains details for one aspect of the current
state of this API Resource.\n---\nThis struct is intended for state of this API Resource.
direct use as an array at the field path .status.conditions. For
example,\n\n\n\ttype FooStatus struct{\n\t // Represents the
observations of a foo's current state.\n\t // Known .status.conditions.type
are: \"Available\", \"Progressing\", and \"Degraded\"\n\t //
+patchMergeKey=type\n\t // +patchStrategy=merge\n\t // +listType=map\n\t
\ // +listMapKey=type\n\t Conditions []metav1.Condition `json:\"conditions,omitempty\"
patchStrategy:\"merge\" patchMergeKey:\"type\" protobuf:\"bytes,1,rep,name=conditions\"`\n\n\n\t
\ // other fields\n\t}"
properties: properties:
lastTransitionTime: lastTransitionTime:
description: |- description: |-
@ -325,12 +314,7 @@ spec:
- Unknown - Unknown
type: string type: string
type: type:
description: |- description: type of condition in CamelCase or in foo.example.com/CamelCase.
type of condition in CamelCase or in foo.example.com/CamelCase.
---
Many .condition.type values are consistent across resources like Available, but because arbitrary conditions can be
useful (see .node.status.conditions), the ability to deconflict is important.
The regex it matches is (dns1123SubdomainFmt/)?(qualifiedNameFmt)
maxLength: 316 maxLength: 316
pattern: ^([a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*/)?(([A-Za-z0-9][-A-Za-z0-9_.]*)?[A-Za-z0-9])$ pattern: ^([a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*/)?(([A-Za-z0-9][-A-Za-z0-9_.]*)?[A-Za-z0-9])$
type: string type: string
@ -683,22 +667,15 @@ spec:
description: URL is the HTTP address of this artifact. description: URL is the HTTP address of this artifact.
type: string type: string
required: required:
- lastUpdateTime
- path - path
- url - url
type: object type: object
conditions: conditions:
description: Conditions holds the conditions for the GitRepository. description: Conditions holds the conditions for the GitRepository.
items: items:
description: "Condition contains details for one aspect of the current description: Condition contains details for one aspect of the current
state of this API Resource.\n---\nThis struct is intended for state of this API Resource.
direct use as an array at the field path .status.conditions. For
example,\n\n\n\ttype FooStatus struct{\n\t // Represents the
observations of a foo's current state.\n\t // Known .status.conditions.type
are: \"Available\", \"Progressing\", and \"Degraded\"\n\t //
+patchMergeKey=type\n\t // +patchStrategy=merge\n\t // +listType=map\n\t
\ // +listMapKey=type\n\t Conditions []metav1.Condition `json:\"conditions,omitempty\"
patchStrategy:\"merge\" patchMergeKey:\"type\" protobuf:\"bytes,1,rep,name=conditions\"`\n\n\n\t
\ // other fields\n\t}"
properties: properties:
lastTransitionTime: lastTransitionTime:
description: |- description: |-
@ -739,12 +716,7 @@ spec:
- Unknown - Unknown
type: string type: string
type: type:
description: |- description: type of condition in CamelCase or in foo.example.com/CamelCase.
type of condition in CamelCase or in foo.example.com/CamelCase.
---
Many .condition.type values are consistent across resources like Available, but because arbitrary conditions can be
useful (see .node.status.conditions), the ability to deconflict is important.
The regex it matches is (dns1123SubdomainFmt/)?(qualifiedNameFmt)
maxLength: 316 maxLength: 316
pattern: ^([a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*/)?(([A-Za-z0-9][-A-Za-z0-9_.]*)?[A-Za-z0-9])$ pattern: ^([a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*/)?(([A-Za-z0-9][-A-Za-z0-9_.]*)?[A-Za-z0-9])$
type: string type: string
@ -784,6 +756,7 @@ spec:
description: URL is the HTTP address of this artifact. description: URL is the HTTP address of this artifact.
type: string type: string
required: required:
- lastUpdateTime
- path - path
- url - url
type: object type: object
@ -952,7 +925,6 @@ spec:
description: |- description: |-
Commit SHA to check out, takes precedence over all reference fields. Commit SHA to check out, takes precedence over all reference fields.
This can be combined with Branch to shallow clone the branch, in which This can be combined with Branch to shallow clone the branch, in which
the commit is expected to exist. the commit is expected to exist.
type: string type: string
@ -960,7 +932,6 @@ spec:
description: |- description: |-
Name of the reference to check out; takes precedence over Branch, Tag and SemVer. Name of the reference to check out; takes precedence over Branch, Tag and SemVer.
It must be a valid Git reference: https://git-scm.com/docs/git-check-ref-format#_description It must be a valid Git reference: https://git-scm.com/docs/git-check-ref-format#_description
Examples: "refs/heads/main", "refs/tags/v0.1.0", "refs/pull/420/head", "refs/merge-requests/1/head" Examples: "refs/heads/main", "refs/tags/v0.1.0", "refs/pull/420/head", "refs/merge-requests/1/head"
type: string type: string
@ -1087,16 +1058,8 @@ spec:
conditions: conditions:
description: Conditions holds the conditions for the GitRepository. description: Conditions holds the conditions for the GitRepository.
items: items:
description: "Condition contains details for one aspect of the current description: Condition contains details for one aspect of the current
state of this API Resource.\n---\nThis struct is intended for state of this API Resource.
direct use as an array at the field path .status.conditions. For
example,\n\n\n\ttype FooStatus struct{\n\t // Represents the
observations of a foo's current state.\n\t // Known .status.conditions.type
are: \"Available\", \"Progressing\", and \"Degraded\"\n\t //
+patchMergeKey=type\n\t // +patchStrategy=merge\n\t // +listType=map\n\t
\ // +listMapKey=type\n\t Conditions []metav1.Condition `json:\"conditions,omitempty\"
patchStrategy:\"merge\" patchMergeKey:\"type\" protobuf:\"bytes,1,rep,name=conditions\"`\n\n\n\t
\ // other fields\n\t}"
properties: properties:
lastTransitionTime: lastTransitionTime:
description: |- description: |-
@ -1137,12 +1100,7 @@ spec:
- Unknown - Unknown
type: string type: string
type: type:
description: |- description: type of condition in CamelCase or in foo.example.com/CamelCase.
type of condition in CamelCase or in foo.example.com/CamelCase.
---
Many .condition.type values are consistent across resources like Available, but because arbitrary conditions can be
useful (see .node.status.conditions), the ability to deconflict is important.
The regex it matches is (dns1123SubdomainFmt/)?(qualifiedNameFmt)
maxLength: 316 maxLength: 316
pattern: ^([a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*/)?(([A-Za-z0-9][-A-Za-z0-9_.]*)?[A-Za-z0-9])$ pattern: ^([a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*/)?(([A-Za-z0-9][-A-Za-z0-9_.]*)?[A-Za-z0-9])$
type: string type: string
@ -1166,7 +1124,6 @@ spec:
changed. changed.
It has the format of `<algo>:<checksum>`, for example: `sha256:<checksum>`. It has the format of `<algo>:<checksum>`, for example: `sha256:<checksum>`.
Deprecated: Replaced with explicit fields for observed artifact content Deprecated: Replaced with explicit fields for observed artifact content
config in the status. config in the status.
type: string type: string

60
config/crd/bases/source.toolkit.fluxcd.io_helmcharts.yaml
View File

@ -3,7 +3,7 @@ apiVersion: apiextensions.k8s.io/v1
kind: CustomResourceDefinition kind: CustomResourceDefinition
metadata: metadata:
annotations: annotations:
controller-gen.kubebuilder.io/version: v0.15.0 controller-gen.kubebuilder.io/version: v0.16.1
name: helmcharts.source.toolkit.fluxcd.io name: helmcharts.source.toolkit.fluxcd.io
spec: spec:
group: source.toolkit.fluxcd.io group: source.toolkit.fluxcd.io
@ -252,16 +252,8 @@ spec:
conditions: conditions:
description: Conditions holds the conditions for the HelmChart. description: Conditions holds the conditions for the HelmChart.
items: items:
description: "Condition contains details for one aspect of the current description: Condition contains details for one aspect of the current
state of this API Resource.\n---\nThis struct is intended for state of this API Resource.
direct use as an array at the field path .status.conditions. For
example,\n\n\n\ttype FooStatus struct{\n\t // Represents the
observations of a foo's current state.\n\t // Known .status.conditions.type
are: \"Available\", \"Progressing\", and \"Degraded\"\n\t //
+patchMergeKey=type\n\t // +patchStrategy=merge\n\t // +listType=map\n\t
\ // +listMapKey=type\n\t Conditions []metav1.Condition `json:\"conditions,omitempty\"
patchStrategy:\"merge\" patchMergeKey:\"type\" protobuf:\"bytes,1,rep,name=conditions\"`\n\n\n\t
\ // other fields\n\t}"
properties: properties:
lastTransitionTime: lastTransitionTime:
description: |- description: |-
@ -302,12 +294,7 @@ spec:
- Unknown - Unknown
type: string type: string
type: type:
description: |- description: type of condition in CamelCase or in foo.example.com/CamelCase.
type of condition in CamelCase or in foo.example.com/CamelCase.
---
Many .condition.type values are consistent across resources like Available, but because arbitrary conditions can be
useful (see .node.status.conditions), the ability to deconflict is important.
The regex it matches is (dns1123SubdomainFmt/)?(qualifiedNameFmt)
maxLength: 316 maxLength: 316
pattern: ^([a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*/)?(([A-Za-z0-9][-A-Za-z0-9_.]*)?[A-Za-z0-9])$ pattern: ^([a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*/)?(([A-Za-z0-9][-A-Za-z0-9_.]*)?[A-Za-z0-9])$
type: string type: string
@ -538,22 +525,15 @@ spec:
description: URL is the HTTP address of this artifact. description: URL is the HTTP address of this artifact.
type: string type: string
required: required:
- lastUpdateTime
- path - path
- url - url
type: object type: object
conditions: conditions:
description: Conditions holds the conditions for the HelmChart. description: Conditions holds the conditions for the HelmChart.
items: items:
description: "Condition contains details for one aspect of the current description: Condition contains details for one aspect of the current
state of this API Resource.\n---\nThis struct is intended for state of this API Resource.
direct use as an array at the field path .status.conditions. For
example,\n\n\n\ttype FooStatus struct{\n\t // Represents the
observations of a foo's current state.\n\t // Known .status.conditions.type
are: \"Available\", \"Progressing\", and \"Degraded\"\n\t //
+patchMergeKey=type\n\t // +patchStrategy=merge\n\t // +listType=map\n\t
\ // +listMapKey=type\n\t Conditions []metav1.Condition `json:\"conditions,omitempty\"
patchStrategy:\"merge\" patchMergeKey:\"type\" protobuf:\"bytes,1,rep,name=conditions\"`\n\n\n\t
\ // other fields\n\t}"
properties: properties:
lastTransitionTime: lastTransitionTime:
description: |- description: |-
@ -594,12 +574,7 @@ spec:
- Unknown - Unknown
type: string type: string
type: type:
description: |- description: type of condition in CamelCase or in foo.example.com/CamelCase.
type of condition in CamelCase or in foo.example.com/CamelCase.
---
Many .condition.type values are consistent across resources like Available, but because arbitrary conditions can be
useful (see .node.status.conditions), the ability to deconflict is important.
The regex it matches is (dns1123SubdomainFmt/)?(qualifiedNameFmt)
maxLength: 316 maxLength: 316
pattern: ^([a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*/)?(([A-Za-z0-9][-A-Za-z0-9_.]*)?[A-Za-z0-9])$ pattern: ^([a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*/)?(([A-Za-z0-9][-A-Za-z0-9_.]*)?[A-Za-z0-9])$
type: string type: string
@ -903,16 +878,8 @@ spec:
conditions: conditions:
description: Conditions holds the conditions for the HelmChart. description: Conditions holds the conditions for the HelmChart.
items: items:
description: "Condition contains details for one aspect of the current description: Condition contains details for one aspect of the current
state of this API Resource.\n---\nThis struct is intended for state of this API Resource.
direct use as an array at the field path .status.conditions. For
example,\n\n\n\ttype FooStatus struct{\n\t // Represents the
observations of a foo's current state.\n\t // Known .status.conditions.type
are: \"Available\", \"Progressing\", and \"Degraded\"\n\t //
+patchMergeKey=type\n\t // +patchStrategy=merge\n\t // +listType=map\n\t
\ // +listMapKey=type\n\t Conditions []metav1.Condition `json:\"conditions,omitempty\"
patchStrategy:\"merge\" patchMergeKey:\"type\" protobuf:\"bytes,1,rep,name=conditions\"`\n\n\n\t
\ // other fields\n\t}"
properties: properties:
lastTransitionTime: lastTransitionTime:
description: |- description: |-
@ -953,12 +920,7 @@ spec:
- Unknown - Unknown
type: string type: string
type: type:
description: |- description: type of condition in CamelCase or in foo.example.com/CamelCase.
type of condition in CamelCase or in foo.example.com/CamelCase.
---
Many .condition.type values are consistent across resources like Available, but because arbitrary conditions can be
useful (see .node.status.conditions), the ability to deconflict is important.
The regex it matches is (dns1123SubdomainFmt/)?(qualifiedNameFmt)
maxLength: 316 maxLength: 316
pattern: ^([a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*/)?(([A-Za-z0-9][-A-Za-z0-9_.]*)?[A-Za-z0-9])$ pattern: ^([a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*/)?(([A-Za-z0-9][-A-Za-z0-9_.]*)?[A-Za-z0-9])$
type: string type: string

66
config/crd/bases/source.toolkit.fluxcd.io_helmrepositories.yaml
View File

@ -3,7 +3,7 @@ apiVersion: apiextensions.k8s.io/v1
kind: CustomResourceDefinition kind: CustomResourceDefinition
metadata: metadata:
annotations: annotations:
controller-gen.kubebuilder.io/version: v0.15.0 controller-gen.kubebuilder.io/version: v0.16.1
name: helmrepositories.source.toolkit.fluxcd.io name: helmrepositories.source.toolkit.fluxcd.io
spec: spec:
group: source.toolkit.fluxcd.io group: source.toolkit.fluxcd.io
@ -89,19 +89,16 @@ spec:
CertSecretRef can be given the name of a Secret containing CertSecretRef can be given the name of a Secret containing
either or both of either or both of
- a PEM-encoded client certificate (`tls.crt`) and private - a PEM-encoded client certificate (`tls.crt`) and private
key (`tls.key`); key (`tls.key`);
- a PEM-encoded CA certificate (`ca.crt`) - a PEM-encoded CA certificate (`ca.crt`)
and whichever are supplied, will be used for connecting to the and whichever are supplied, will be used for connecting to the
registry. The client cert and key are useful if you are registry. The client cert and key are useful if you are
authenticating with a certificate; the CA cert is useful if authenticating with a certificate; the CA cert is useful if
you are using a self-signed server certificate. The Secret must you are using a self-signed server certificate. The Secret must
be of type `Opaque` or `kubernetes.io/tls`. be of type `Opaque` or `kubernetes.io/tls`.
It takes precedence over the values specified in the Secret referred It takes precedence over the values specified in the Secret referred
to by `.spec.secretRef`. to by `.spec.secretRef`.
properties: properties:
@ -243,16 +240,8 @@ spec:
conditions: conditions:
description: Conditions holds the conditions for the HelmRepository. description: Conditions holds the conditions for the HelmRepository.
items: items:
description: "Condition contains details for one aspect of the current description: Condition contains details for one aspect of the current
state of this API Resource.\n---\nThis struct is intended for state of this API Resource.
direct use as an array at the field path .status.conditions. For
example,\n\n\n\ttype FooStatus struct{\n\t // Represents the
observations of a foo's current state.\n\t // Known .status.conditions.type
are: \"Available\", \"Progressing\", and \"Degraded\"\n\t //
+patchMergeKey=type\n\t // +patchStrategy=merge\n\t // +listType=map\n\t
\ // +listMapKey=type\n\t Conditions []metav1.Condition `json:\"conditions,omitempty\"
patchStrategy:\"merge\" patchMergeKey:\"type\" protobuf:\"bytes,1,rep,name=conditions\"`\n\n\n\t
\ // other fields\n\t}"
properties: properties:
lastTransitionTime: lastTransitionTime:
description: |- description: |-
@ -293,12 +282,7 @@ spec:
- Unknown - Unknown
type: string type: string
type: type:
description: |- description: type of condition in CamelCase or in foo.example.com/CamelCase.
type of condition in CamelCase or in foo.example.com/CamelCase.
---
Many .condition.type values are consistent across resources like Available, but because arbitrary conditions can be
useful (see .node.status.conditions), the ability to deconflict is important.
The regex it matches is (dns1123SubdomainFmt/)?(qualifiedNameFmt)
maxLength: 316 maxLength: 316
pattern: ^([a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*/)?(([A-Za-z0-9][-A-Za-z0-9_.]*)?[A-Za-z0-9])$ pattern: ^([a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*/)?(([A-Za-z0-9][-A-Za-z0-9_.]*)?[A-Za-z0-9])$
type: string type: string
@ -474,22 +458,15 @@ spec:
description: URL is the HTTP address of this artifact. description: URL is the HTTP address of this artifact.
type: string type: string
required: required:
- lastUpdateTime
- path - path
- url - url
type: object type: object
conditions: conditions:
description: Conditions holds the conditions for the HelmRepository. description: Conditions holds the conditions for the HelmRepository.
items: items:
description: "Condition contains details for one aspect of the current description: Condition contains details for one aspect of the current
state of this API Resource.\n---\nThis struct is intended for state of this API Resource.
direct use as an array at the field path .status.conditions. For
example,\n\n\n\ttype FooStatus struct{\n\t // Represents the
observations of a foo's current state.\n\t // Known .status.conditions.type
are: \"Available\", \"Progressing\", and \"Degraded\"\n\t //
+patchMergeKey=type\n\t // +patchStrategy=merge\n\t // +listType=map\n\t
\ // +listMapKey=type\n\t Conditions []metav1.Condition `json:\"conditions,omitempty\"
patchStrategy:\"merge\" patchMergeKey:\"type\" protobuf:\"bytes,1,rep,name=conditions\"`\n\n\n\t
\ // other fields\n\t}"
properties: properties:
lastTransitionTime: lastTransitionTime:
description: |- description: |-
@ -530,12 +507,7 @@ spec:
- Unknown - Unknown
type: string type: string
type: type:
description: |- description: type of condition in CamelCase or in foo.example.com/CamelCase.
type of condition in CamelCase or in foo.example.com/CamelCase.
---
Many .condition.type values are consistent across resources like Available, but because arbitrary conditions can be
useful (see .node.status.conditions), the ability to deconflict is important.
The regex it matches is (dns1123SubdomainFmt/)?(qualifiedNameFmt)
maxLength: 316 maxLength: 316
pattern: ^([a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*/)?(([A-Za-z0-9][-A-Za-z0-9_.]*)?[A-Za-z0-9])$ pattern: ^([a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*/)?(([A-Za-z0-9][-A-Za-z0-9_.]*)?[A-Za-z0-9])$
type: string type: string
@ -641,19 +613,16 @@ spec:
CertSecretRef can be given the name of a Secret containing CertSecretRef can be given the name of a Secret containing
either or both of either or both of
- a PEM-encoded client certificate (`tls.crt`) and private - a PEM-encoded client certificate (`tls.crt`) and private
key (`tls.key`); key (`tls.key`);
- a PEM-encoded CA certificate (`ca.crt`) - a PEM-encoded CA certificate (`ca.crt`)
and whichever are supplied, will be used for connecting to the and whichever are supplied, will be used for connecting to the
registry. The client cert and key are useful if you are registry. The client cert and key are useful if you are
authenticating with a certificate; the CA cert is useful if authenticating with a certificate; the CA cert is useful if
you are using a self-signed server certificate. The Secret must you are using a self-signed server certificate. The Secret must
be of type `Opaque` or `kubernetes.io/tls`. be of type `Opaque` or `kubernetes.io/tls`.
It takes precedence over the values specified in the Secret referred It takes precedence over the values specified in the Secret referred
to by `.spec.secretRef`. to by `.spec.secretRef`.
properties: properties:
@ -795,16 +764,8 @@ spec:
conditions: conditions:
description: Conditions holds the conditions for the HelmRepository. description: Conditions holds the conditions for the HelmRepository.
items: items:
description: "Condition contains details for one aspect of the current description: Condition contains details for one aspect of the current
state of this API Resource.\n---\nThis struct is intended for state of this API Resource.
direct use as an array at the field path .status.conditions. For
example,\n\n\n\ttype FooStatus struct{\n\t // Represents the
observations of a foo's current state.\n\t // Known .status.conditions.type
are: \"Available\", \"Progressing\", and \"Degraded\"\n\t //
+patchMergeKey=type\n\t // +patchStrategy=merge\n\t // +listType=map\n\t
\ // +listMapKey=type\n\t Conditions []metav1.Condition `json:\"conditions,omitempty\"
patchStrategy:\"merge\" patchMergeKey:\"type\" protobuf:\"bytes,1,rep,name=conditions\"`\n\n\n\t
\ // other fields\n\t}"
properties: properties:
lastTransitionTime: lastTransitionTime:
description: |- description: |-
@ -845,12 +806,7 @@ spec:
- Unknown - Unknown
type: string type: string
type: type:
description: |- description: type of condition in CamelCase or in foo.example.com/CamelCase.
type of condition in CamelCase or in foo.example.com/CamelCase.
---
Many .condition.type values are consistent across resources like Available, but because arbitrary conditions can be
useful (see .node.status.conditions), the ability to deconflict is important.
The regex it matches is (dns1123SubdomainFmt/)?(qualifiedNameFmt)
maxLength: 316 maxLength: 316
pattern: ^([a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*/)?(([A-Za-z0-9][-A-Za-z0-9_.]*)?[A-Za-z0-9])$ pattern: ^([a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*/)?(([A-Za-z0-9][-A-Za-z0-9_.]*)?[A-Za-z0-9])$
type: string type: string

25
config/crd/bases/source.toolkit.fluxcd.io_ocirepositories.yaml
View File

@ -3,7 +3,7 @@ apiVersion: apiextensions.k8s.io/v1
kind: CustomResourceDefinition kind: CustomResourceDefinition
metadata: metadata:
annotations: annotations:
controller-gen.kubebuilder.io/version: v0.15.0 controller-gen.kubebuilder.io/version: v0.16.1
name: ocirepositories.source.toolkit.fluxcd.io name: ocirepositories.source.toolkit.fluxcd.io
spec: spec:
group: source.toolkit.fluxcd.io group: source.toolkit.fluxcd.io
@ -59,19 +59,16 @@ spec:
CertSecretRef can be given the name of a Secret containing CertSecretRef can be given the name of a Secret containing
either or both of either or both of
- a PEM-encoded client certificate (`tls.crt`) and private - a PEM-encoded client certificate (`tls.crt`) and private
key (`tls.key`); key (`tls.key`);
- a PEM-encoded CA certificate (`ca.crt`) - a PEM-encoded CA certificate (`ca.crt`)
and whichever are supplied, will be used for connecting to the and whichever are supplied, will be used for connecting to the
registry. The client cert and key are useful if you are registry. The client cert and key are useful if you are
authenticating with a certificate; the CA cert is useful if authenticating with a certificate; the CA cert is useful if
you are using a self-signed server certificate. The Secret must you are using a self-signed server certificate. The Secret must
be of type `Opaque` or `kubernetes.io/tls`. be of type `Opaque` or `kubernetes.io/tls`.
Note: Support for the `caFile`, `certFile` and `keyFile` keys have Note: Support for the `caFile`, `certFile` and `keyFile` keys have
been deprecated. been deprecated.
properties: properties:
@ -313,16 +310,8 @@ spec:
conditions: conditions:
description: Conditions holds the conditions for the OCIRepository. description: Conditions holds the conditions for the OCIRepository.
items: items:
description: "Condition contains details for one aspect of the current description: Condition contains details for one aspect of the current
state of this API Resource.\n---\nThis struct is intended for state of this API Resource.
direct use as an array at the field path .status.conditions. For
example,\n\n\n\ttype FooStatus struct{\n\t // Represents the
observations of a foo's current state.\n\t // Known .status.conditions.type
are: \"Available\", \"Progressing\", and \"Degraded\"\n\t //
+patchMergeKey=type\n\t // +patchStrategy=merge\n\t // +listType=map\n\t
\ // +listMapKey=type\n\t Conditions []metav1.Condition `json:\"conditions,omitempty\"
patchStrategy:\"merge\" patchMergeKey:\"type\" protobuf:\"bytes,1,rep,name=conditions\"`\n\n\n\t
\ // other fields\n\t}"
properties: properties:
lastTransitionTime: lastTransitionTime:
description: |- description: |-
@ -363,12 +352,7 @@ spec:
- Unknown - Unknown
type: string type: string
type: type:
description: |- description: type of condition in CamelCase or in foo.example.com/CamelCase.
type of condition in CamelCase or in foo.example.com/CamelCase.
---
Many .condition.type values are consistent across resources like Available, but because arbitrary conditions can be
useful (see .node.status.conditions), the ability to deconflict is important.
The regex it matches is (dns1123SubdomainFmt/)?(qualifiedNameFmt)
maxLength: 316 maxLength: 316
pattern: ^([a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*/)?(([A-Za-z0-9][-A-Za-z0-9_.]*)?[A-Za-z0-9])$ pattern: ^([a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*/)?(([A-Za-z0-9][-A-Za-z0-9_.]*)?[A-Za-z0-9])$
type: string type: string
@ -391,7 +375,6 @@ spec:
artifact needs to be rebuilt. artifact needs to be rebuilt.
It has the format of `<algo>:<checksum>`, for example: `sha256:<checksum>`. It has the format of `<algo>:<checksum>`, for example: `sha256:<checksum>`.
Deprecated: Replaced with explicit fields for observed artifact content Deprecated: Replaced with explicit fields for observed artifact content
config in the status. config in the status.
type: string type: string

124
config/rbac/role.yaml
View File

@ -23,125 +23,9 @@ rules:
- source.toolkit.fluxcd.io - source.toolkit.fluxcd.io
resources: resources:
- buckets - buckets
verbs:
- create
- delete
- get
- list
- patch
- update
- watch
- apiGroups:
- source.toolkit.fluxcd.io
resources:
- buckets/finalizers
verbs:
- create
- delete
- get
- patch
- update
- apiGroups:
- source.toolkit.fluxcd.io
resources:
- buckets/status
verbs:
- get
- patch
- update
- apiGroups:
- source.toolkit.fluxcd.io
resources:
- gitrepositories - gitrepositories
verbs:
- create
- delete
- get
- list
- patch
- update
- watch
- apiGroups:
- source.toolkit.fluxcd.io
resources:
- gitrepositories/finalizers
verbs:
- create
- delete
- get
- patch
- update
- apiGroups:
- source.toolkit.fluxcd.io
resources:
- gitrepositories/status
verbs:
- get
- patch
- update
- apiGroups:
- source.toolkit.fluxcd.io
resources:
- helmcharts - helmcharts
verbs:
- create
- delete
- get
- list
- patch
- update
- watch
- apiGroups:
- source.toolkit.fluxcd.io
resources:
- helmcharts/finalizers
verbs:
- create
- delete
- get
- patch
- update
- apiGroups:
- source.toolkit.fluxcd.io
resources:
- helmcharts/status
verbs:
- get
- patch
- update
- apiGroups:
- source.toolkit.fluxcd.io
resources:
- helmrepositories - helmrepositories
verbs:
- create
- delete
- get
- list
- patch
- update
- watch
- apiGroups:
- source.toolkit.fluxcd.io
resources:
- helmrepositories/finalizers
verbs:
- create
- delete
- get
- patch
- update
- apiGroups:
- source.toolkit.fluxcd.io
resources:
- helmrepositories/status
verbs:
- get
- patch
- update
- apiGroups:
- source.toolkit.fluxcd.io
resources:
- ocirepositories - ocirepositories
verbs: verbs:
- create - create
@ -154,6 +38,10 @@ rules:
- apiGroups: - apiGroups:
- source.toolkit.fluxcd.io - source.toolkit.fluxcd.io
resources: resources:
- buckets/finalizers
- gitrepositories/finalizers
- helmcharts/finalizers
- helmrepositories/finalizers
- ocirepositories/finalizers - ocirepositories/finalizers
verbs: verbs:
- create - create
@ -164,6 +52,10 @@ rules:
- apiGroups: - apiGroups:
- source.toolkit.fluxcd.io - source.toolkit.fluxcd.io
resources: resources:
- buckets/status
- gitrepositories/status
- helmcharts/status
- helmrepositories/status
- ocirepositories/status - ocirepositories/status
verbs: verbs:
- get - get