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

Network policy to allow LTPA job to connect to k8s API service #545

Open
leochr opened this issue Feb 8, 2024 · 2 comments
Open

Network policy to allow LTPA job to connect to k8s API service #545

leochr opened this issue Feb 8, 2024 · 2 comments

Comments

@leochr
Copy link
Member

leochr commented Feb 8, 2024

Create an egress network policy to allow the LTPA Job to access the k8s API service (kubernetes.default.svc).

Service address can't be referred in network policies. Instead look up the IP address of the API service and use it instead. Operator pod should be injected with the service details as an env variable

@kabicin kabicin self-assigned this Feb 12, 2024
@kabicin
Copy link
Member

kabicin commented Feb 29, 2024

Fix is ready for review for WLO WASdev/websphere-liberty-operator#615, if that looks good I can also port the changes to OLO.

@kabicin
Copy link
Member

kabicin commented Apr 23, 2024

Rebased onto main and fixed small issue with the bundle.
WLO: WASdev/websphere-liberty-operator#615
OLO: #573
Tests: https://github.ibm.com/websphere/operators/pull/123

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

No branches or pull requests

2 participants