Skip to content
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

Merged
merged 7 commits into from
Aug 22, 2024

Conversation

akgalwas
Copy link
Contributor

@akgalwas akgalwas commented Aug 16, 2024

Description

Changes proposed in this pull request:

  • Exemplary Runtime CR yamls fixed
  • Status condition contains detailed error message from Gardener (temporary solution, in the future we must provide error category in the CR's status)

Related issue(s)
#332

@akgalwas akgalwas requested a review from a team as a code owner August 16, 2024 08:33
@kyma-bot kyma-bot added cla: yes Indicates the PR's author has signed the CLA. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Aug 16, 2024
@kyma-bot kyma-bot added area/documentation Issues or PRs related to documentation size/M Denotes a PR that changes 30-99 lines, ignoring generated files. and removed size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Aug 16, 2024
@kyma-bot kyma-bot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. and removed size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Aug 16, 2024
@akgalwas akgalwas changed the title Gardener error message added to the status condition Runtime CR examples updated Aug 16, 2024
# spec.shoot.purpose is required
purpose: evaluation
# spec.shoot.region is required
region: eu-central-1
region: polandcentral
Copy link
Member

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"
Copy link
Member

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?

Copy link
Member

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

Copy link
Contributor Author

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

Copy link
Contributor Author

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
Copy link
Member

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.

Copy link
Contributor Author

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

Copy link
Member

@Disper Disper left a 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?

@Disper
Copy link
Member

Disper commented Aug 21, 2024

I've managed to test succesfully the examples for

  • aws-freemium
  • azure-lite ( I had to do this change in order to make it work)
  • gcp

@akgalwas akgalwas mentioned this pull request Aug 22, 2024
23 tasks
@akgalwas
Copy link
Contributor Author

Azure, GCP and CCEE contains additionalOidcConfig: sections while other examples do not. Is it intentional?

The following yamls : aws, azure, gcp, sap-converged-cloud are supposed to contain all the fields that KEB can specify. Examples prefixed with trial, freemium, lite, or minimal are supposed to be smaller so they doesn't contain additionalOidcConfig section on purpose.

@kyma-bot kyma-bot added the lgtm Looks good to me! label Aug 22, 2024
@kyma-bot kyma-bot merged commit 356fed3 into kyma-project:main Aug 22, 2024
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/documentation Issues or PRs related to documentation cla: yes Indicates the PR's author has signed the CLA. lgtm Looks good to me! size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants