The application development team is pushing a Kubernetes application into production. I consists of an application server and a database. The team wants to ensure that only the production…

Question

Options

• AYes, by using kubect1 to create a Network Policy that only allows pods on the same network
• BYes. by logging in to NSX Manager and creating a firewall rules to only allow the production
• CYes, by using kubect1 to create a policy that disables pod to pod communication in the
• DNo, Kubernetes Network Policy does not support this action.

• A
  74% (23)
• B
  3% (1)
• C
  13% (4)
• D
  10% (3)

Explanation

If you want to control traffic flow at the IP address or port level (OSI layer 3 or 4), then you might consider using Kubernetes NetworkPolicies for particular applications in your cluster. NetworkPolicies are an application-centric construct which allow you to specify how a pod is allowed to communicate with various network "entities" (we use the word "entity" here to avoid overloading the more common terms such as "endpoints" and "services", which have specific Kubernetes connotations) over the network. NetworkPolicies apply to a connection with a pod on one or both ends, and are not relevant to other connections.

No community discussion yet for this question.