Be able to ignore ports to expose in a katenary.io/ports list #16

New Issue

metal3d · 2022-05-21T08:01:03Z

adrian-salas commented

2022-05-21 08:01:03 +00:00

(Migrated from github.com)

Sometimes when declaring multiple ports with the katenary.io/ports label, all of the list might not need to be exposed.

eg
We declare the following ports
katenary.io/ports: 80,443,8080,9000

In a PHP-Nginx configuration, the 9000 port shouldn't b exposed as it is only used internally.

We could ave a second label that is used to "declare" the internal ports, so it is not exposed

Sometimes when declaring multiple ports with the katenary.io/ports label, all of the list might not need to be exposed. eg We declare the following ports `katenary.io/ports: 80,443,8080,9000` In a PHP-Nginx configuration, the 9000 port shouldn't b exposed as it is only used internally. We could ave a second label that is used to "declare" the internal ports, so it is not exposed

metal3d commented

2022-06-10 10:19:06 +00:00

I wonder how we can declare this.
At this time we declare ports to be in "containerPort" in pods and "port" in services.
I propose:

katenary.io/ports: N
katenary.io/containerPorts: M

if "ports" is declared, it creates the containerPort in pods and the port in service
if "containerPorts" is declared, it only creates ports in pods but not in service
if both, so merge the definitions

Right ?

I wonder how we can declare this. At this time we declare ports to be in "containerPort" in pods and "port" in services. I propose: ``` katenary.io/ports: N katenary.io/containerPorts: M ``` - if "ports" is declared, it creates the containerPort in pods **and** the port in service - if "containerPorts" is declared, it **only** creates ports in pods but **not** in service - if both, so merge the definitions Right ?

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: Katenary/katenary#16