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

Creating network policy for opentofu runner #1104

Merged
merged 2 commits into from
May 15, 2024

Conversation

sudhir-kelkar
Copy link
Contributor

@sudhir-kelkar sudhir-kelkar commented May 14, 2024

This PR creates network policy for Opentofu runner.

  • Network policy name will be ibm-infra-management-application-allow-tfrunner
  • It will generate spec something like this
spec:
  podSelector:
    matchLabels:
      service: opentofu
  ingress:
    - ports:
        - protocol: TCP
          port: 6000
      from:
        - podSelector:
            matchLabels:
              name: orchestrator
        - podSelector:
            matchLabels:
              ibm-infra-management-application-orchestrated-by: orchestrator-765bdbcdfc-kfrht

@sudhir-kelkar sudhir-kelkar changed the title WIP: Creating network policy for opentofu runner Creating network policy for opentofu runner May 15, 2024
@sudhir-kelkar sudhir-kelkar changed the title Creating network policy for opentofu runner WIP: Creating network policy for opentofu runner May 15, 2024
@miq-bot
Copy link
Member

miq-bot commented May 15, 2024

Checked commits sudhir-kelkar/manageiq-pods@fe516be~...eb601a5 with ruby 2.7.8, rubocop 1.56.3, haml-lint 0.51.0, and yamllint
0 files checked, 0 offenses detected
Everything looks fine. ⭐

@sudhir-kelkar sudhir-kelkar changed the title WIP: Creating network policy for opentofu runner Creating network policy for opentofu runner May 15, 2024
@bdunne bdunne merged commit 2ed3cb7 into ManageIQ:master May 15, 2024
2 checks passed
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.

None yet

4 participants