Support multiple manifests in K8s Services
long-term
C
Corporate Hornet
Helm Services currently support multiple manifests but, K8s services do not. We'd like the ability to add multiple manifests to our Services so we can select them at run time or use an expression to dynamically switch them.
Log In
I
Isolated Cat
We recently ran into issues deploying a Service into an OpenShift Project in our SMP-based environment. The issue seems related to the use of an older delegate where this failed. It was/is working with the tag in other Projects using newer delegates. Updating the older delegate "fixed" the issue.
However, I'm left wondering (and not finding much documentation) on what Fetch Type we should be using if we want to support branches and tags? Some searching suggests using "gitFetchType: Commit"? The documentation focused on the UI, but doesn't provide much additional detail.
Before we update our Service definitions for multiple applications, what is the Harness-recommended approach to handling branches and tags?
With the fetchType set to branch, it somehow works for both Branches and Tags?!
However, this is clearly a grey area — especially since we noticed different behavior in different delegate versions.
Is the officially supported Harness position 2 Services? Or Commit for branch or tag (a bit less friendly for those less git savvy)?
a
abhijit.pujare
marked this post as
long-term
a
abhijit.pujare
Thank you for submitting the feature request. We have added it to our backlog.