Federation internal port should not be created when federation is disabled

[gregoryboue]

Since version 107.68.7 and this release :

• Disabled federation services when splitServicesToContainers=true

The templates services now have a new internal port http-rtfs.

I think that this port configuration should not be done when artifactory.federation.enabled=false.

Version of Helm and Kubernetes:
All

Which chart:
Since 107.68.7

Which product license (Enterprise/Pro/oss):
All

What happened:

An internal port is created for artifactory federation service even if federation is disabled.

What you expected to happen:

That the port is not present in artifactory service template when ederation is disabled

[chukka]

Already fixed as part of 7.98.x SH release

[bengaywins]

@chukka Can you elaborate on which release please? Because we're on 7.98.9 and it definitely is not fixed. And I looked through the release notes and cannot find a reference to this being fixed.

[chukka]

@bengaywins As I see in 107.98.9 chart , in artifactory-service.yaml

  {{- if .Values.federation.enabled }}
  - port: {{ .Values.federation.internalPort }}
    targetPort: {{ .Values.federation.internalPort }}
    protocol: TCP
    name: http-rtfs
  {{- end }}

its fixed in 107.94.x (internal release )

[bengaywins]

Great thank you! Appreciate the prompt response!