chore: Replacing KubernetesServicePatch with ops.set_ports #28
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
gruyaume
approved these changes
Dec 1, 2023
Gmerold
deleted the
TELCO-882-using-ops-set-ports-instead-of-kubernetes-service-patch
branch
patriciareinoso
pushed a commit
that referenced
this pull request
Dec 6, 2023
Update dependency eslint to v8.45.0
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 PR replaces
KubernetesServicePatchwithops.set_portsfor setting the ports exposed by the workload.It's worth noting, that with ops.set_ports we're not able to set custom name for the port. ops will automatically set the name of the port to
juju-{PORT_NUMBER}-tcp.Checklist: