search

kubernetes-retired / cluster-api-provider-nested

Cluster API Provider for Nested Clusters
Apache License 2.0
301 stars 67 forks source link

DNS resolution not working #213

Closed yaron2 closed 2 years ago

yaron2 commented 3 years ago

What steps did you take and what happened: [A clear and concise description on how to REPRODUCE the bug.]

Trying to connect to pods using Kubernetes Services results in connection refused errors.

What did you expect to happen:

Kubernetes services are working.

Anything else you would like to add:

Installed master branch version of VC on an AKS cluster.

When trying to access Service DNS, the addresses are unreachable. Here's an example of a kubectl apply -f command that executes a registered webhook validation:

error when creating "nginx.yaml": Internal error occurred: failed calling webhook "vvalidator.kb.io": Post https://k8s-validation-webhooks-service.default.svc:443/validate-app-microsoft-com-v1alpha1-app?timeout=10s: context deadline exceeded

Containers running in a tenant namespace also cannot access DNS based services. They can, however, access Pod IPs directly.

DNS works fine in the super cluster environment.

Environment:

/kind bug

Fei-Guo commented 3 years ago

Have you looked at this document https://github.com/kubernetes-sigs/cluster-api-provider-nested/blob/main/virtualcluster/doc/tenant-dns.md ?

k8s-triage-robot commented 2 years ago

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot commented 2 years ago

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

k8s-triage-robot commented 2 years ago

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

k8s-ci-robot commented 2 years ago

@k8s-triage-robot: Closing this issue.

In response to [this](https://github.com/kubernetes-sigs/cluster-api-provider-nested/issues/213#issuecomment-1035333129): >The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. > >This bot triages issues and PRs according to the following rules: >- After 90d of inactivity, `lifecycle/stale` is applied >- After 30d of inactivity since `lifecycle/stale` was applied, `lifecycle/rotten` is applied >- After 30d of inactivity since `lifecycle/rotten` was applied, the issue is closed > >You can: >- Reopen this issue or PR with `/reopen` >- Mark this issue or PR as fresh with `/remove-lifecycle rotten` >- Offer to help out with [Issue Triage][1] > >Please send feedback to sig-contributor-experience at [kubernetes/community](https://github.com/kubernetes/community). > >/close > >[1]: https://www.kubernetes.dev/docs/guide/issue-triage/ Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.