-
Notifications
You must be signed in to change notification settings - Fork 690
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
Contour Fails to read TLSCertificateDelegation objects #977
Labels
kind/bug
Categorizes issue or PR as related to a bug.
priority/critical-urgent
Highest priority. Must be actively worked on as someone's top priority right now.
Milestone
Comments
Delegations is a list, I think you have a scalar there.
… On 5 Apr 2019, at 14:12, joshrosso ***@***.***> wrote:
To Reproduce
Bootstrap a new Kubernetes cluster with kubeadm.
Deploy contour
kubectl apply -f https://j.hept.io/contour-deployment-rbac
Create an ingress-system namespace.
kubectl create ns ingress-system
Add the following TLSCertificateDelegation object
apiVersion: contour.heptio.com/v1beta1
kind: TLSCertificateDelegation
metadata:
name: octetz-tls
namespace: ingress-system
spec:
delegations:
secretName: octetz-tls
targetNamespaces:
- mountains
- trails
Tail the logs for a contour pod.
kubectl logs -n contour $(kubectl -n contour get pod -l app=contour -o jsonpath='{.items[0].metadata.name}') -c contour
note that in my case I've deployed contour in the namespace contour.
Observe the watcher failing to decode slice.
E0405 03:09:42.564058 1 reflector.go:205] github.com/heptio/contour/internal/k8s/watcher.go:73: Failed to list *v1beta1.TLSCertificateDelegation: v1beta1.TLSCertificateDelegationList.Items: []v1beta1.TLSCertificateDelegation: v1beta1.TLSCertificateDelegation.Spec: v1beta1.TLSCertificateDelegationSpec.Delegations: []v1beta1.CertificateDelegation: decode slice: expect [ or n, but found {, error found in #10 byte of ...|gations":{"secretNam|..., bigger context ...|0-11e9-96f7-5254002b90c2"},"spec":{"delegations":{"secretName":"octetz-tls","targetNamespaces":["mou|...
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Got it, so perhaps we have a documentation issue on our hands then? |
Yup, my bad. Yet another place where we don't have tests of nuanced yaml.
…On Fri, 5 Apr 2019 at 14:33, joshrosso ***@***.***> wrote:
Got it, so perhaps we have a documentation issue on our hands then?
https://github.com/heptio/contour/blob/master/docs/ingressroute.md#tls-certificate-delegation
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#977 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAAcAw1C5ZU0QsavQIYHNiEVPWrUqLr5ks5vdsQXgaJpZM4ceFQS>
.
|
davecheney
added a commit
to davecheney/contour
that referenced
this issue
Apr 5, 2019
Fixes projectcontour#977 Also correct documentation that incorrectly stated that spec.delegations was a singular key. Signed-off-by: Dave Cheney <[email protected]>
davecheney
added
kind/bug
Categorizes issue or PR as related to a bug.
priority/critical-urgent
Highest priority. Must be actively worked on as someone's top priority right now.
labels
Apr 5, 2019
Got it, thanks for following up @davecheney. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
kind/bug
Categorizes issue or PR as related to a bug.
priority/critical-urgent
Highest priority. Must be actively worked on as someone's top priority right now.
To Reproduce
Bootstrap a new Kubernetes cluster with
kubeadm
.Deploy contour
Create an
ingress-system
namespace.Add the TLS secret to the
ingress-system
namespace.Add the following TLSCertificateDelegation object
Tail the logs for a contour pod.
Observe the watcher failing to decode slice.
The text was updated successfully, but these errors were encountered: