Skip to content

outdated/deprecated ingress apiVersion #17330

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

Open
kundan2707 opened this issue Mar 27, 2025 · 6 comments
Open

outdated/deprecated ingress apiVersion #17330

kundan2707 opened this issue Mar 27, 2025 · 6 comments
Assignees
Labels
kind/bug Categorizes issue or PR as related to a bug. sig/network Categorizes an issue or PR as relevant to SIG Network.

Comments

@kundan2707
Copy link
Contributor

/kind bug

1. What kops version are you running? The command kops version, will display
this information.

1.31.0

2. What Kubernetes version are you running? kubectl version will print the
version if a cluster is running or provide the Kubernetes version specified as
a kops flag.

1.32
3. What cloud provider are you using?
baremetal
4. What commands did you run? What is the simplest way to reproduce this issue?
kubectl apply -f https://raw.githubusercontent.com/kubernetes/contrib/master/ingress/controllers/nginx/examples/ingress.yaml
5. What happened after the commands executed?
error
6. What did you expect to happen?
it should create ingress resource
7. Please provide your cluster manifest. Execute
kops get --name my.example.com -o yaml to display your cluster manifest.
You may want to remove your cluster name and other sensitive information.

8. Please run the commands with most verbose logging by adding the -v 10 flag.
Paste the logs into this report, or in a gist and provide the gist link here.

9. Anything else do we need to know?

@k8s-ci-robot k8s-ci-robot added the kind/bug Categorizes issue or PR as related to a bug. label Mar 27, 2025
@kundan2707
Copy link
Contributor Author

error: resource mapping not found for name: "echomap" namespace: "" from "https://raw.githubusercontent.com/kubernetes/contrib/master/ingress/controllers/nginx/examples/ingress.yaml": no matches for kind "Ingress" in version "extensions/v1beta1"
ensure CRDs are installed first

@kundan2707
Copy link
Contributor Author

@kundan2707
Copy link
Contributor Author

https://github.com/kubernetes-retired/contrib/blob/master/ingress/controllers/nginx/examples/ingress.yaml

this repo was already archived in 2019. we should create new yaml file in kops repo to work correctly

@kundan2707
Copy link
Contributor Author

/assign

@kundan2707
Copy link
Contributor Author

kubectl run echoheaders --image=registry.k8s.io/echoserver:1.4 --replicas=1 --port=8080
This command also needs to be updated as kubectl run with --replicas option deprecated long time ago

@kundan2707
Copy link
Contributor Author

/sig network

@k8s-ci-robot k8s-ci-robot added the sig/network Categorizes an issue or PR as relevant to SIG Network. label Mar 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. sig/network Categorizes an issue or PR as relevant to SIG Network.
Projects
None yet
Development

No branches or pull requests

2 participants