-
Notifications
You must be signed in to change notification settings - Fork 405
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
Migrate kyma provision gardener
to using kubectl against gardener seed cluster
#18674
Comments
Minimal example configs: GCPapiVersion: core.gardener.cloud/v1beta1
kind: Shoot
metadata:
name: test
spec:
secretBindingName: secretName
cloudProfileName: gcp
region: europe-west1
purpose: evaluation
provider:
type: gcp
infrastructureConfig:
apiVersion: gcp.provider.extensions.gardener.cloud/v1alpha1
kind: InfrastructureConfig
networks:
workers: 10.250.0.0/16
controlPlaneConfig:
apiVersion: gcp.provider.extensions.gardener.cloud/v1alpha1
kind: ControlPlaneConfig
zone: europe-west1-b
workers:
- name: cpu-worker
minimum: 1
maximum: 2
machine:
type: n1-standard-4
volume:
type: pd-standard
size: 20Gi
zones:
- europe-west1-b
networking:
type: calico
pods: 100.96.0.0/11
nodes: 10.250.0.0/16
services: 100.64.0.0/13 AWSapiVersion: core.gardener.cloud/v1beta1
kind: Shoot
metadata:
name: test
spec:
secretBindingName: secretName
cloudProfileName: aws
region: eu-west-1
purpose: evaluation
provider:
type: aws
infrastructureConfig:
apiVersion: aws.provider.extensions.gardener.cloud/v1alpha1
kind: InfrastructureConfig
networks:
vpc:
cidr: 10.250.0.0/16
zones:
- name: eu-west-1b
internal: 10.250.112.0/22
public: 10.250.96.0/22
workers: 10.250.0.0/19
workers:
- name: cpu-worker
minimum: 1
maximum: 2
machine:
type: m5.large
volume:
type: gp2
size: 20Gi
zones:
- eu-west-1b
networking:
type: calico
pods: 100.96.0.0/11
nodes: 10.250.0.0/16
services: 100.64.0.0/13 AzureapiVersion: core.gardener.cloud/v1beta1
kind: Shoot
metadata:
name: test
spec:
secretBindingName: secretName
cloudProfileName: az
region: westeurope
purpose: evaluation
provider:
type: azure
infrastructureConfig:
apiVersion: azure.provider.extensions.gardener.cloud/v1alpha1
kind: InfrastructureConfig
networks:
vnet:
cidr: 10.250.0.0/16
workers: 10.250.0.0/19
workers:
- name: cpu-worker
minimum: 1
maximum: 2
machine:
type: Standard_A4_v2
volume:
type: Standard_LRS
size: 20Gi
networking:
type: calico
pods: 100.96.0.0/11
nodes: 10.250.0.0/16
services: 100.64.0.0/13 |
This was referenced May 16, 2024
8 tasks
This was referenced May 22, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
Update docs and shell scripts which use
kyma provision gardener
command.Migrate from deprecated cli command into applying shoot manifests directly (docs)
Do not enforce shoot parameters if they are not required. Let gardener defaulting mechanism default values that are not provided (i.e k8s version)
Reasons
kyma cli commands to provision k8s clusters are deprecated and will be removed from kyma cli. Those not be used.
Decision
kyma-project/cli#2051
The text was updated successfully, but these errors were encountered: