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

Federation internal port should not be created when federation is disabled #1849

Open
gregoryboue opened this issue Dec 11, 2023 · 0 comments
Labels
bug Something isn't working triaged

Comments

@gregoryboue
Copy link

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

@gitta-jfrog gitta-jfrog added triaged bug Something isn't working labels Dec 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working triaged
Projects
None yet
Development

No branches or pull requests

2 participants