Enables relevant ActiveGate service ports based on capability requirements #622
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This changeset solves the problem deploying ActiveGate with capabilities which require a
ClusterIP
service (routing
,dynatrace-api
) but withoutmetrics-ingest
.Before that, defining
routiung
and/ordynatrace-api
withoutmetrics-ingest
caused deployment failure due to AG service not exposing HTTP(S) ports, with stack trace similar to:How can this be tested?
Automatic
Run or inspect kuttl test scenario
tests/activegate/routing
.Manual
To test the fix, experiment with ActiveGate capabilities making sure that the expected service ports are exposed (and the AG pod is ready):
routing
,dynatrace-api
and/ormetrics-ingest
capabilities are defined, portshttp
andhttps
are exposed indynakube-activegate
statsd-ingest
is enabled, portstatsd
is exposed indynakube-activegate
statsd-ingest
and at least one ofrouting
,dynatrace-api
and/ormetrics-ingest
are enabled, all the three ports are exposed (http
,https
,statsd
)kubernetes-monitoring
only, the AG service is not created at alldynakube-activegate
(or is removed)Checklist