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

Backport of catalog: improve the bound workload identity encoding on services into release/1.18.x #20467

Conversation

hc-github-team-consul-core
Copy link
Collaborator

Backport

This PR is auto-generated from #20458 to be assessed for backporting due to the inclusion of the label backport/1.18.

The below text is copied from the body of the original PR.


Description

The endpoints controller currently encodes the list of unique workload identities referenced by all workload matched by a Service into a special data-bearing status condition on that Service. This allows a downstream controller to avoid an expensive watch on the ServiceEndpoints type just to get this data.

The current encoding does not lend itself well to machine parsing, which is what the field is meant for, so this PR simplifies the encoding from:

"blah blah: " + strings.Join(ids, ",") + "."

to

strings.Join(ids, ",")

It also provides an exported utility function to easily extract this data.

PR Checklist

  • updated test coverage
  • [ ] external facing docs updated
  • appropriate backport labels added
  • not a security concern

Overview of commits

@hc-github-team-consul-core hc-github-team-consul-core force-pushed the backport/rboyer/change-service-wi-cond-formatting/unlikely-brief-anemone branch from f7bf091 to a6ecb97 Compare February 2, 2024 22:28
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Auto approved Consul Bot automated PR

…0458)

The endpoints controller currently encodes the list of unique workload identities 
referenced by all workload matched by a Service into a special data-bearing 
status condition on that Service. This allows a downstream controller to avoid an 
expensive watch on the ServiceEndpoints type just to get this data.

The current encoding does not lend itself well to machine parsing, which is what 
the field is meant for, so this PR simplifies the encoding from:

    "blah blah: " + strings.Join(ids, ",") + "."

to

    strings.Join(ids, ",")

It also provides an exported utility function to easily extract this data.
@rboyer rboyer force-pushed the backport/rboyer/change-service-wi-cond-formatting/unlikely-brief-anemone branch from a6ecb97 to 2531c83 Compare February 2, 2024 22:29
@rboyer rboyer enabled auto-merge (squash) February 2, 2024 22:29
@rboyer rboyer merged commit a49f2d0 into release/1.18.x Feb 2, 2024
89 checks passed
@rboyer rboyer deleted the backport/rboyer/change-service-wi-cond-formatting/unlikely-brief-anemone branch February 2, 2024 22:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants