Closed aboncok closed 5 months ago
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues 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
/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.
This bot triages un-triaged issues 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 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 not-planned
@k8s-triage-robot: Closing this issue, marking it as "Not Planned".
Hi,
I have successfully deployed HNC on an OCI OKE kubernetes cluster, I am trying to configure my local kubectl to be able to configure HNC on the cluster. When I try to run kubectl-hns_windows_amd64.exe, I always get
context deadline exceeded
error back.For me to communicate with the OKE cluster, I have to setup what is called an OCI Bastion session which is just an ssh port-forward session. The authentication is somewhat special: OCI needs to generate a token and for that to work, kubectl first has to call OCI to get the auth token.
Maybe this causes a timeout in the hnc plugin, however, I only get that
context deadline exceeded
message back with no further information. What can I do to make this work?v1.1.0