-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Runtime CR examples updated #345
Conversation
# spec.shoot.purpose is required | ||
purpose: evaluation | ||
# spec.shoot.region is required | ||
region: eu-central-1 | ||
region: polandcentral |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
what was your intention with this change?
# spec.shoot.worker.zones is required | ||
zones: | ||
- 1 | ||
- "1" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why is this quotation necessary?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also, couldn't we use the actual regions here to omit the number of things someone has to change in the CR to make it work? We have such zones listed in e.g. aws-trial example
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why is this quotation necessary?
When quotation is missed we will get the following error:
The Runtime "azure-lite" is invalid: spec.shoot.provider.workers[0].zones[0]: Invalid value: "integer": spec.shoot.provider.workers[0].zones[0] in body must be of type string: "integer"
Kubernetes expects string field, as zones
have the following definition in the CRD:
zones:
description: |-
Zones is a list of availability zones that are used to evenly distribute this worker pool. Optional as not every provider may support availability zones.
items:
type: string
type: array
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also, couldn't we use the actual regions here to omit the number of things someone has to change in the CR to make it work? We have such zones listed in e.g. aws-trial example
We do use actual regions. polandcentral
was introduced in the last year and is fully supported by Gardener.
namespace: kcp-system | ||
spec: | ||
shoot: | ||
# spec.shoot.name is required | ||
name: shoot-name | ||
name: azure-lite |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
usernameClaim: sub
at line 40 has incorrect indentation and can't be applied.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
usernameClaim: sub
at line 40 has incorrect indentation and can't be applied.
Fixed
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Azure, GCP and CCEE contains additionalOidcConfig:
sections while other examples do not. Is it intentional?
I've managed to test succesfully the examples for
|
The following yamls : |
Description
Changes proposed in this pull request:
Related issue(s)
#332