Skip to content

Commit

Permalink
Update to k8s 1.24 toolchain (#11)
Browse files Browse the repository at this point in the history
Signed-off-by: Pulak Kanti Bhowmick <pulak@appscode.com>
  • Loading branch information
pkbhowmick authored Jul 22, 2022
1 parent 0be39c9 commit 29c2b04
Show file tree
Hide file tree
Showing 2,629 changed files with 232,415 additions and 86,294 deletions.
4 changes: 1 addition & 3 deletions .config/api-rules/violation_exceptions.list
Original file line number Diff line number Diff line change
Expand Up @@ -28,10 +28,8 @@ API rule violation: list_type_missing,k8s.io/api/core/v1,EphemeralContainerCommo
API rule violation: list_type_missing,k8s.io/api/core/v1,EphemeralContainerCommon,Command
API rule violation: list_type_missing,k8s.io/api/core/v1,EphemeralContainerCommon,Env
API rule violation: list_type_missing,k8s.io/api/core/v1,EphemeralContainerCommon,EnvFrom
API rule violation: list_type_missing,k8s.io/api/core/v1,EphemeralContainerCommon,Ports
API rule violation: list_type_missing,k8s.io/api/core/v1,EphemeralContainerCommon,VolumeDevices
API rule violation: list_type_missing,k8s.io/api/core/v1,EphemeralContainerCommon,VolumeMounts
API rule violation: list_type_missing,k8s.io/api/core/v1,EphemeralContainers,EphemeralContainers
API rule violation: list_type_missing,k8s.io/api/core/v1,ExecAction,Command
API rule violation: list_type_missing,k8s.io/api/core/v1,FCVolumeSource,TargetWWNs
API rule violation: list_type_missing,k8s.io/api/core/v1,FCVolumeSource,WWIDs
Expand Down Expand Up @@ -99,7 +97,6 @@ API rule violation: list_type_missing,k8s.io/api/core/v1,ServiceAccount,ImagePul
API rule violation: list_type_missing,k8s.io/api/core/v1,ServiceAccount,Secrets
API rule violation: list_type_missing,k8s.io/api/core/v1,ServiceSpec,ExternalIPs
API rule violation: list_type_missing,k8s.io/api/core/v1,ServiceSpec,LoadBalancerSourceRanges
API rule violation: list_type_missing,k8s.io/api/core/v1,ServiceSpec,TopologyKeys
API rule violation: list_type_missing,k8s.io/api/core/v1,TopologySelectorLabelRequirement,Values
API rule violation: list_type_missing,k8s.io/api/core/v1,TopologySelectorTerm,MatchLabelExpressions
API rule violation: list_type_missing,k8s.io/api/rbac/v1,AggregationRule,ClusterRoleSelectors
Expand Down Expand Up @@ -188,6 +185,7 @@ API rule violation: names_match,k8s.io/apimachinery/pkg/apis/meta/v1,Duration,Du
API rule violation: names_match,k8s.io/apimachinery/pkg/apis/meta/v1,InternalEvent,Object
API rule violation: names_match,k8s.io/apimachinery/pkg/apis/meta/v1,InternalEvent,Type
API rule violation: names_match,k8s.io/apimachinery/pkg/apis/meta/v1,MicroTime,Time
API rule violation: names_match,k8s.io/apimachinery/pkg/apis/meta/v1,ObjectMeta,ZZZ_DeprecatedClusterName
API rule violation: names_match,k8s.io/apimachinery/pkg/apis/meta/v1,StatusCause,Type
API rule violation: names_match,k8s.io/apimachinery/pkg/apis/meta/v1,Time,Time
API rule violation: names_match,k8s.io/apimachinery/pkg/runtime,Unknown,ContentEncoding
Expand Down
2 changes: 1 addition & 1 deletion Makefile
Original file line number Diff line number Diff line change
Expand Up @@ -25,7 +25,7 @@ COMPRESS ?= no

# Produce CRDs that work back to Kubernetes 1.11 (no version conversion)
CRD_OPTIONS ?= "crd:crdVersions={v1},allowDangerousTypes=true"
CODE_GENERATOR_IMAGE ?= appscode/gengo:release-1.21
CODE_GENERATOR_IMAGE ?= appscode/gengo:release-1.24
API_GROUPS ?= supervisor:v1alpha1

# Where to push the docker image.
Expand Down
2,162 changes: 1,230 additions & 932 deletions apis/supervisor/v1alpha1/openapi_generated.go

Large diffs are not rendered by default.

7 changes: 3 additions & 4 deletions crds/supervisor.appscode.com_clustermaintenancewindows.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -46,7 +46,7 @@ spec:
description: 'Dates consists of a list of Dates as Maintenance time.
Dates are always needed to be given in UTC format. Format: yyyy-mm-ddThh.mm.ssZ
[Here Z stands for Zero time zone / UTC time zone / GMT (+0000)]
Example: dates: - start: 2022-01-24T00:00:18Z end: 2022-01-24T23:41:18Z'
Example: dates: - start: 2022-01-24T00:00:18Z end: 2022-01-24T23:41:18Z'
items:
properties:
end:
Expand Down Expand Up @@ -77,8 +77,7 @@ spec:
type: array
description: 'Days consists of a map of DayOfWeek and corresponding
list of TimeWindow. There is `Logical OR` relationship between Days
and Dates. Example: days: Monday: - start: 10:40AM end:
7:00PM'
and Dates. Example: days: Monday: - start: 10:40AM end: 7:00PM'
type: object
isDefault:
type: boolean
Expand All @@ -88,7 +87,7 @@ spec:
the given times and dates are considered as server local timezone.
\n Otherwise, the Timezone should specify a location name corresponding
to a file in the IANA Time Zone database, such as \"Asia/Dhaka\",
\"America/New_York\", . Ref: https://www.iana.org/time-zones https://en.wikipedia.org/wiki/List_of_tz_database_time_zones"
\"America/New_York\", . Ref: https://www.iana.org/time-zones https://en.wikipedia.org/wiki/List_of_tz_database_time_zones"
type: string
type: object
status:
Expand Down
7 changes: 3 additions & 4 deletions crds/supervisor.appscode.com_maintenancewindows.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -45,7 +45,7 @@ spec:
description: 'Dates consists of a list of Dates as Maintenance time.
Dates are always needed to be given in UTC format. Format: yyyy-mm-ddThh.mm.ssZ
[Here Z stands for Zero time zone / UTC time zone / GMT (+0000)]
Example: dates: - start: 2022-01-24T00:00:18Z end: 2022-01-24T23:41:18Z'
Example: dates: - start: 2022-01-24T00:00:18Z end: 2022-01-24T23:41:18Z'
items:
properties:
end:
Expand Down Expand Up @@ -76,8 +76,7 @@ spec:
type: array
description: 'Days consists of a map of DayOfWeek and corresponding
list of TimeWindow. There is `Logical OR` relationship between Days
and Dates. Example: days: Monday: - start: 10:40AM end:
7:00PM'
and Dates. Example: days: Monday: - start: 10:40AM end: 7:00PM'
type: object
isDefault:
type: boolean
Expand All @@ -87,7 +86,7 @@ spec:
the given times and dates are considered as server local timezone.
\n Otherwise, the Timezone should specify a location name corresponding
to a file in the IANA Time Zone database, such as \"Asia/Dhaka\",
\"America/New_York\", . Ref: https://www.iana.org/time-zones https://en.wikipedia.org/wiki/List_of_tz_database_time_zones"
\"America/New_York\", . Ref: https://www.iana.org/time-zones https://en.wikipedia.org/wiki/List_of_tz_database_time_zones"
type: string
type: object
status:
Expand Down
34 changes: 17 additions & 17 deletions crds/supervisor.appscode.com_recommendations.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -92,29 +92,29 @@ spec:
description: 'Rules defines OperationPhaseRules. It contains three
identification rules of successful execution of the operation, progressing
execution of the operation & failed execution of the operation.
Example: rules: success: `has(self.status.phase) && self.status.phase
== ''Successful''` inProgress: `has(self.status.phase) && self.status.phase
== ''Progressing''` failed: `has(self.status.phase) && self.status.phase
Example: rules: success: `has(self.status.phase) && self.status.phase
== ''Successful''` inProgress: `has(self.status.phase) && self.status.phase
== ''Progressing''` failed: `has(self.status.phase) && self.status.phase
== ''Failed''`'
properties:
failed:
description: 'Failed defines a rule to identify that applied operation
is failed. Example: inProgress: `has(self.status.phase) &&
self.status.phase == ''Failed''` Here self.status.phase is pointing
to .status.phase field of the Operation object. When .status.phase
field presents and becomes `Failed`, the Failed rule will satisfy.'
is failed. Example: inProgress: `has(self.status.phase) && self.status.phase
== ''Failed''` Here self.status.phase is pointing to .status.phase
field of the Operation object. When .status.phase field presents
and becomes `Failed`, the Failed rule will satisfy.'
type: string
inProgress:
description: 'InProgress defines a rule to identify that applied
operation is progressing. Example: inProgress: `has(self.status.phase)
operation is progressing. Example: inProgress: `has(self.status.phase)
&& self.status.phase == ''Progressing''` Here self.status.phase
is pointing to .status.phase field of the Operation object.
When .status.phase field presents and becomes `Progressing`,
the InProgress rule will satisfy.'
type: string
success:
description: 'Success defines a rule to identify the successful
execution of the operation. Example: success: `has(self.status.phase)
execution of the operation. Example: success: `has(self.status.phase)
&& self.status.phase == ''Successful''` Here self.status.phase
is pointing to .status.phase field of the Operation object.
When .status.phase field presents and becomes `Successful`,
Expand Down Expand Up @@ -308,14 +308,14 @@ spec:
phase:
description: 'Specifies the Recommendation current phase. Possible
values are: Pending : Recommendation misses at least one pre-requisite
for executing the operation. It also tells that some user
action is needed. Skipped : Operation is skipped because of Rejection
ApprovalStatus. Waiting : Recommendation is waiting for the MaintenanceWindow
to execute the operation or waiting for others Recommendation
to complete far maintaining Parallelism. InProgress : The operation
execution is successfully started and waiting for its final status.
Succeeded : Operation has been successfully executed. Failed : Operation
execution has not completed successfully i.e. encountered an error'
for executing the operation. It also tells that some user action
is needed. Skipped : Operation is skipped because of Rejection ApprovalStatus.
Waiting : Recommendation is waiting for the MaintenanceWindow to
execute the operation or waiting for others Recommendation to complete
far maintaining Parallelism. InProgress : The operation execution
is successfully started and waiting for its final status. Succeeded
: Operation has been successfully executed. Failed : Operation execution
has not completed successfully i.e. encountered an error'
enum:
- Pending
- Skipped
Expand Down
Loading

0 comments on commit 29c2b04

Please sign in to comment.