Skip to content
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

Enable inverse proxy to access host network #2614

Merged
merged 1 commit into from
Nov 18, 2019
Merged

Conversation

IronPan
Copy link
Member

@IronPan IronPan commented Nov 15, 2019

When switching to GKE workload identity, the pods can't access to metadata server anymore by default due to metadata concealment.
This can be unlocked by explicitly enable hostnetwork for the pod.
https://cloud.google.com/kubernetes-engine/docs/how-to/protecting-cluster-metadata#concealment

This should be OK as proxy is an optional component. In any case when user feel this not a secure option he/she could opt out it.

/assign @Bobgy


This change is Reviewable

When switching to GKE workload identity, the pods can't access to metadata server anymore by default due to metadata concealment. 
This can be unlocked by explicitly enable hostnetwork for the pod. 
https://cloud.google.com/kubernetes-engine/docs/how-to/protecting-cluster-metadata#concealment

This should be OK as proxy is an optional component. In any case when user feel this not a secure option he/she could opt out it.
@Bobgy
Copy link
Contributor

Bobgy commented Nov 18, 2019

Thanks for figuring out the fix! I also verified it works with workload identity.

/lgtm
/approve

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Bobgy

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants