-
Notifications
You must be signed in to change notification settings - Fork 687
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
Unable to create Host
resource due to tls cert error from emissary-apiext
#5728
Comments
Am I correct in thinking that the certificate in question is the value of apiVersion: apiextensions.k8s.io/v1
kind: CustomResourceDefinition
metadata:
generation: 2
labels:
app.kubernetes.io/instance: emissary-apiext
app.kubernetes.io/managed-by: kubectl_apply_-f_emissary-apiext.yaml
app.kubernetes.io/name: emissary-apiext
app.kubernetes.io/part-of: emissary-apiext
name: hosts.getambassador.io
resourceVersion: "244433"
uid: ef8bf370-0ca4-485c-859d-2a083a67db40
spec:
conversion:
strategy: Webhook
webhook:
clientConfig:
caBundle: LS0t...0tLQo= |
something i noticed after running the b64 decoded
whereas the CRD's status:
acceptedNames:
categories:
- ambassador-crds
kind: Host
listKind: HostList
plural: hosts
singular: host
conditions:
- lastTransitionTime: "2024-07-25T12:09:21Z"
message: no conflicts found
reason: NoConflicts
status: "True"
type: NamesAccepted
- lastTransitionTime: "2024-07-25T12:09:21Z"
message: the initial names have been accepted
reason: InitialNamesAccepted
status: "True"
type: Established
storedVersions:
- v2 and the cert error from above was at |
suspect these logs from
|
seems related to #5468 which afaik is not included in |
Yes, at a glance it does seem that fix could be related and was merged after the v.3.9.1 release. Future releases of Emissary will depend on the maintainers collectively so that schedule is currently undecided. It's possible to build Emissary from source to capture PRs that have been merged but not yet released in a new version, if you wanted to test that. |
Is there a discussion or anything that relates to recent news regarding the future of emissary releases? We would only be able to target stable releases/patch fixes |
also after investigating patches, i think this is likely to be the fix for our particular issue c8edb16 - once it gets released anyway |
@fs185143 We're looking into an Emissary 3.10 that will include that fix -- watch this space. 🙂 |
Describe the bug
Cannot create
Host
resource after upgradingemissary-apiext
andemissary-ingress
To Reproduce
Steps to reproduce the behavior:
Host
resource on an environment running ambassador2.0.4
2.0.4
to3.9.1
emissary-apiext
start as expectedHost
resource againemissary-apiext
logs:emissary/emissary-ingress
deployment fails indefinitely as it includes thisHost
emissary-apiext
pod inemissary-system
namespaceHost
applies fine andemissary-ingress
deployment can proceedExpected behavior
A clear and concise description of what you expected to happen.
Should be able to apply
Host
without getting above webhook error fromemissary-system/emissary-apiext
Versions (please complete the following information):
Additional context
Wondering if some sort of race condition is occurring
The text was updated successfully, but these errors were encountered: