Closed yaron2 closed 2 years ago
Have you looked at this document https://github.com/kubernetes-sigs/cluster-api-provider-nested/blob/main/virtualcluster/doc/tenant-dns.md ?
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:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
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:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
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:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/reopen
/remove-lifecycle rotten
Please send feedback to sig-contributor-experience at kubernetes/community.
/close
@k8s-triage-robot: Closing this issue.
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: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:
kubectl version
): 1.20.7/etc/os-release
): Ubuntu/kind bug