GKE: Kubernetes 1.19 or later is required to use Ingress in networking.k8s.io/v1
See original GitHub issueHello!
- Vote on this issue by adding a 👍 reaction
- To contribute a fix for this issue, leave a comment (and link to your pull request, if you’ve opened one already)
Issue details
Hi,
I am trying to deploy the cloudbees-core
helm chart using the 3.40.1+0dc0318c25a4
version on a GKE cluster (version 1.21
):
core = kubernetes.helm.v3.Release(
"core",
args=kubernetes.helm.v3.ReleaseArgs(
name="cloudbees-core",
chart="cloudbees-core",
version="3.40.1+0dc0318c25a4",
namespace="cloudbees-core",
repository_opts=kubernetes.helm.v3.RepositoryOptsArgs(
repo="https://charts.cloudbees.com/public/cloudbees",
),
),
opts=ResourceOptions(provider=k8s_provider),
)
But:
$ pulumi preview
Previewing update (dev):
Type Name Plan Info
+ pulumi:pulumi:Stack gcp-gke-dev create
+ ├─ gcp:organizations:Project project create
+ ├─ gcp:projects:Service compute create
+ ├─ gcp:projects:Service container create
+ ├─ gcp:compute:Network vpc create
+ ├─ gcp:compute:Subnetwork gke create
+ ├─ gcp:container:Cluster cluster create
+ ├─ gcp:container:NodePool pool-n2-4 create
+ ├─ pulumi:providers:kubernetes k8s create
+ ├─ kubernetes:core/v1:Namespace core-ns create
└─ kubernetes:helm.sh/v3:Release core 1 error
Diagnostics:
kubernetes:helm.sh/v3:Release (core):
error: failed to create chart from template: execution error at (cloudbees-core/templates/cjoc-ingress.yaml:2:4):
ERROR: Kubernetes 1.19 or later is required to use Ingress in networking.k8s.io/v1
I am not sure how to pass the kubernetes/GKE version.
helm install ...
is working after just deploying the GKE cluster, so pulumi is not able to understand which kubernetes version will be run.
Any ideas?
Thanks
Issue Analytics
- State:
- Created 2 years ago
- Reactions:2
- Comments:32 (15 by maintainers)
Top Results From Across the Web
GKE Ingress for HTTP(S) Load Balancing - Google Cloud
This controller implements Ingress resources as Google Cloud load balancers for HTTP(S) workloads in GKE. Note: In Kubernetes version 1.19 and later, the ......
Read more >Open side panel - You.com
kubernetes /websiteerror: unable to recognize "example-ingress.yaml": no matches for kind "Ingress" in version "networking.k8s.io/v1beta1"#14322.
Read more >Getting Started with Runtime Fabric on Google Kubernetes ...
Create a Google Kubernetes Engine (GKE) cluster using gcloud; Use kubectl to ... apiVersion: networking.k8s.io/v1 kind: Ingress metadata: annotations: ...
Read more >google_container_cluster | Resources | hashicorp/google
See the Using GKE with Terraform guide for more information about using GKE with Terraform. Manages a Google Kubernetes Engine (GKE) cluster.
Read more >Incident affecting Google Kubernetes Engine
Issues with GKE 1.20 (lower than 1.20.9-gke.2100) node pools using Docker as runtime. ... If you have experienced impact outside of what is...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Drats, it looks like our
Check
function renders the chart template in order to work out what resources will be created and this happens in ClientOnly mode.I’ll need to defer to @viveklak and @lblackstone, I’m not sure if it’s possible to navigate around this atm.
Hi @rawkode, we are also facing this issue. Have you managed to find a solution (with a different helm chart the root cause is the some)? Thanks