bzp2010 opened a new pull request, #2880: URL: https://github.com/apache/apisix-ingress-controller/pull/2880
<!-- Please answer these questions before submitting a pull request --> ### Type of change: <!-- Please delete options that are not relevant. --> <!-- Select all the options from below that matches the type your PR best --> - [ ] Bugfix - [x] New feature provided - [ ] Improve performance - [ ] Backport patches - [ ] Documentation - [x] Refactor - [ ] Chore - [ ] CI/CD or Tests What this PR does / why we need it: Part 1 of #2877 This is preparatory groundwork for bad-resource isolation on the APISIX standalone provider (the larger change is being split into several PRs to keep review manageable; this is the first). - Bumps the ADC sidecar to 0.30.5, which fixes a standalone credential-attribution bug the isolation work depends on. - Gives every Consumer credential a stable id (<username>/credentials/<name>), instead of leaving ADC to derive one. Without this, a rejected credential can't be matched back to the Kubernetes credential that produced it. - Adds TypeStreamRoute, TypeUpstream and TypeConsumerCredential to api/adc, naming the nested entity types an ADC event can report (a stream route or named upstream inside a service, a credential inside a consumer). They aren't consumed yet; later PRs in this series use them to attribute rejections against these entities. - Adds ComposeGatewayListenerSSLName and switches the Gateway listener certificate id generation to it, replacing an inline fmt.Sprintf. Same id, just named and reusable. No behavior change other than the credential id, which eping and not user-visible. Pre-submission checklist: - [x] Did you explain what problem does this PR solve? Or what new features have been added? - [x] Have you added corresponding test cases? - [ ] Have you modified the corresponding document? - [x] Is this PR backward compatible? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
