Create a new Network Policy for a specific package through configmap

Hi, I am using Bigbang Release 1.25.1. I am looking to create a new Network Policy to open up Egress LDAP port for a package through configmap for my dev environment. Can you help me get the right syntax to do this within the configmap for a pacakge?

I appreciate all the efforts and help

@micah.nagel @kevin.wilder

assigned to @jasonkrause

@sipvw5 We only n-2 versions of Big Bang. Can you update to a supported version?

@jasonkrause Thank you we are upgrading it to 1.31 now

NetworkPolicies are not created with a configmap. You can create a networkpolicy similar to I instructed you for Nexus
https://repo1.dso.mil/platform-one/big-bang/bigbang/-/issues/1140#note_583680

Thanks @kevin.wilder

This should be sufficient to get you up and running:

• Create a yaml with the networkpolicy like the one Kevin gave you (i.e. nexus-ldap-egress.yaml)
• Place that into your environment folder (i.e. prod/nexus-ldap-egress.yaml, equivalent of this folder depending on environment)
• In the same folder edit the Kustomization (i.e. prod/kustomization.yaml) and add under resources:

  resources:
    - nexus-ldap-egress.yaml

This will deploy the policy as part of the specific environment you included it with.

Note: this doesn't handle any enforcing of deployment order, so you won't have a guarantee that the policy deploys after Nexus. If you wanted to ensure that happens it would be more complex but you could create a Helm chart with your extra manifests and deploy that as a Flux HR with dependencies on Nexus, etc.

Thanks @micah.nagel That worked

Closing the issue

closed