We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
--- apiVersion: compute.gcp.upbound.io/v1beta1 kind: Network metadata: annotations: uptest.upbound.io/timeout: "4800" meta.upbound.io/example-id: compute/v1beta1/network labels: testing.upbound.io/example-name: example_network name: example-network spec: forProvider: autoCreateSubnetworks: false --- apiVersion: compute.gcp.upbound.io/v1beta1 kind: Subnetwork metadata: annotations: meta.upbound.io/example-id: compute/v1beta1/subnetwork labels: testing.upbound.io/example-name: example_subnet name: gke spec: forProvider: ipCidrRange: 10.0.0.0/24 networkSelector: matchLabels: testing.upbound.io/example-name: example_network region: us-central1 privateIpGoogleAccess: true secondaryIpRange: - ipCidrRange: 10.1.0.0/16 rangeName: pods - ipCidrRange: 10.2.0.0/20 rangeName: services --- apiVersion: compute.gcp.upbound.io/v1beta1 kind: Router metadata: annotations: meta.upbound.io/example-id: compute/v1beta1/router labels: testing.upbound.io/example-name: example_router name: example-router spec: forProvider: networkSelector: matchLabels: testing.upbound.io/example-name: example_network region: us-central1 --- apiVersion: compute.gcp.upbound.io/v1beta1 kind: RouterNAT metadata: annotations: meta.upbound.io/example-id: compute/v1beta1/routernat labels: testing.upbound.io/example-name: example_routernat name: example-routernat spec: forProvider: natIpAllocateOption: AUTO_ONLY region: us-central1 routerSelector: matchLabels: testing.upbound.io/example-name: example_router sourceSubnetworkIpRangesToNat: ALL_SUBNETWORKS_ALL_IP_RANGES --- apiVersion: container.gcp.upbound.io/v1beta1 kind: Cluster metadata: annotations: meta.upbound.io/example-id: container/v1beta1/cluster labels: testing.upbound.io/example-name: cluster name: cluster spec: forProvider: addonsConfig: - gcePersistentDiskCsiDriverConfig: - enabled: true gcpFilestoreCsiDriverConfig: - enabled: true gkeBackupAgentConfig: - enabled: true binaryAuthorization: - evaluationMode: PROJECT_SINGLETON_POLICY_ENFORCE datapathProvider: ADVANCED_DATAPATH deletionProtection: false enableAutopilot: false enableIntranodeVisibility: true enableL4IlbSubsetting: true enableShieldedNodes: true gatewayApiConfig: - channel: CHANNEL_STANDARD initialNodeCount: 1 ipAllocationPolicy: - clusterSecondaryRangeName: pods servicesSecondaryRangeName: services location: us-central1 masterAuthorizedNetworksConfig: - gcpPublicCidrsAccessEnabled: false cidrBlocks: - cidrBlock: 10.0.0.0/24 displayName: bastion networkSelector: matchLabels: testing.upbound.io/example-name: example_network networkingMode: VPC_NATIVE privateClusterConfig: - enablePrivateEndpoint: true enablePrivateNodes: true masterGlobalAccessConfig: - enabled: false privateEndpointSubnetwork: gke releaseChannel: - channel: STABLE removeDefaultNodePool: true subnetworkSelector: matchLabels: testing.upbound.io/example-name: example_subnet workloadIdentityConfig: - workloadPool: bradw-nextgen-devops.svc.id.goog
All resources deployed, but the Cluster resource did not delete the default pool after creation when removeDefaultNodePool: true. This worked in v1.7.
removeDefaultNodePool: true
No response
1.6
1.8
The text was updated successfully, but these errors were encountered:
+1
Sorry, something went wrong.
No branches or pull requests
Is there an existing issue for this?
Affected Resource(s)
Resource MRs required to reproduce the bug
Steps to Reproduce
What happened?
All resources deployed, but the Cluster resource did not delete the default pool after creation when
removeDefaultNodePool: true
. This worked in v1.7.Relevant Error Output Snippet
No response
Crossplane Version
1.6
Provider Version
1.8
Kubernetes Version
No response
Kubernetes Distribution
No response
Additional Info
No response
The text was updated successfully, but these errors were encountered: