creating voyager ingress on k8s version 1.20 is failing about voyager HOT 8 OPEN

@sankarpn , please try the https://github.com/voyagermesh/voyager/releases/tag/v13.0.0-rc.0 release. That should work.

from voyager.

Its still not working, I tried both https://artifacthub.io/packages/helm/appscode/voyager/13.0.0-beta.1 and https://artifacthub.io/packages/helm/appscode/voyager/2021.4.24-rc.0

from voyager.

@sankarpn, if you are interested in acquiring license for the Voyager Enterprise, please fill up the form here: https://appscode.com/contact/ . We have stopped doing free work for other businesses.

from voyager.

@tamalsaha We don't use voyager in production. We test and certify that voyager works with our Oracle WebLogic k8s operator in different environments. There are a lot of customers will be using voyager when we certify.

from voyager.

@sankarpn , that's exciting. Could we set up a call to get a better understanding?

from voyager.

My can reach me by email tamal AT appscode.com .

from voyager.

I tried to install version 2021.4.24-rc.0 using the configuration values from https://artifacthub.io/packages/helm/appscode/voyager/2021.4.24-rc.0 , looks like the "operator.tag" doesn't set the release version.

helm install voyager-release50-huha appscode/voyager --namespace ns-huha --set "operator.tag=v13.0.0-rc.0" --set "apiserver.enableValidatingWebhook=true" --set "cloudProvider=baremetal"

As you can see from the following describe it still uses the v12.0.0 version

[opc@olcne-1 ~]$ kubectl describe -n ns-huha pod/voyager-release50-huha-68c5c66d-l5w8m
Name: voyager-release50-huha-68c5c66d-l5w8m
Namespace: ns-huha
Priority: 0
Node: olcne-3/10.0.3.76
Start Time: Fri, 03 Sep 2021 18:07:48 +0000
Labels: app.kubernetes.io/instance=voyager-release50-huha
app.kubernetes.io/name=voyager
pod-template-hash=68c5c66d
Annotations: checksum/apiregistration.yaml: 351fa9985c13336fe4fd47127ed5f6f165a1c79e1c60d6a1296709b9331a4234
Status: Running
IP: 10.244.1.99
IPs:
IP: 10.244.1.99
Controlled By: ReplicaSet/voyager-release50-huha-68c5c66d
Containers:
voyager:
Container ID: cri-o://59d8bc2d720fc76c096536acc022d52c2669c5e1d2f7889e5fe6e7f2f99627d1
Image: appscode/voyager:v12.0.0
Image ID: docker.io/appscode/voyager@sha256:1569c90b098c301fde05efeab508c5adc44c63690e091e9db55e6d362de04adb
Ports: 8443/TCP, 56791/TCP
Host Ports: 0/TCP, 0/TCP
Args:
run
--cloud-provider=baremetal
--cloud-config=
--v=3
--ingress-class=
--operator-service=voyager-release50-huha
--docker-registry=appscode
--haproxy-image-tag=1.9.15-v12.0.0-alpine
--haproxy-image-repository=haproxy
--exporter-image-tag=v12.0.0
--exporter-image-repository=voyager
--secure-port=8443
--audit-log-path=-
--tls-cert-file=/var/serving-cert/tls.crt
--tls-private-key-file=/var/serving-cert/tls.key
--enable-validating-webhook=true
--bypass-validating-webhook-xray=false
--use-kubeapiserver-fqdn-for-aks=true
--enable-analytics=true
State: Running
Started: Fri, 03 Sep 2021 18:07:49 +0000
Ready: True
Restart Count: 0
Environment:
MY_POD_NAME: voyager-release50-huha-68c5c66d-l5w8m (v1:metadata.name)
MY_POD_NAMESPACE: ns-huha (v1:metadata.namespace)
Mounts:
/var/run/secrets/kubernetes.io/serviceaccount from voyager-release50-huha-token-47xvl (ro)
/var/serving-cert from serving-cert (rw)

I had to use the voyager.tag to correctly install the version desired.

helm install voyager-release50-huha appscode/voyager --namespace ns-huha --set "voyager.tag=v13.0.0-rc.0" --set "apiserver.enableValidatingWebhook=true" --set "cloudProvider=baremetal"

[opc@olcne-1 ~]$ kubectl describe -n ns-huha pod/voyager-release50-huha-7f46b9fb6f-9p6lx
Name: voyager-release50-huha-7f46b9fb6f-9p6lx
Namespace: ns-huha
Priority: 0
Node: olcne-3/10.0.3.76
Start Time: Fri, 03 Sep 2021 18:10:39 +0000
Labels: app.kubernetes.io/instance=voyager-release50-huha
app.kubernetes.io/name=voyager
pod-template-hash=7f46b9fb6f
Annotations: checksum/apiregistration.yaml: de5e98866b6881061ef385371c49e7e22da221ac39955760e8da95c6182f9394
Status: Running
IP: 10.244.1.101
IPs:
IP: 10.244.1.101
Controlled By: ReplicaSet/voyager-release50-huha-7f46b9fb6f
Containers:
voyager:
Container ID: cri-o://71c6fcb89bbfbfef3bb735e198a6029eceb4ec36c3f8dfcd9a36c66e9707f7f4
Image: appscode/voyager:v13.0.0-rc.0
Image ID: docker.io/appscode/voyager@sha256:6d35a828ef929c04c5cda70c8013389a2de78035d04bc10c339b585588b5abb0
Ports: 8443/TCP, 56791/TCP
Host Ports: 0/TCP, 0/TCP
Args:
run
--cloud-provider=baremetal
--cloud-config=
--v=3
--ingress-class=
--operator-service=voyager-release50-huha
--docker-registry=appscode
--haproxy-image-tag=1.9.15-v12.0.0-alpine
--haproxy-image-repository=haproxy
--exporter-image-tag=v13.0.0-rc.0
--exporter-image-repository=voyager
--secure-port=8443
--audit-log-path=-
--tls-cert-file=/var/serving-cert/tls.crt
--tls-private-key-file=/var/serving-cert/tls.key
--enable-validating-webhook=true
--bypass-validating-webhook-xray=false
--use-kubeapiserver-fqdn-for-aks=true
--enable-analytics=true

But again look at the --haproxy-image-tag=1.9.15-v12.0.0-alpine which is not matching with the version 1.9.15-v13.0.0-rc.0-alpine.

Also the operator pod kept crashing.

2m11s Normal Created pod/voyager-release50-huha-7f46b9fb6f-9p6lx Created container voyager
2m11s Normal Pulled pod/voyager-release50-huha-7f46b9fb6f-9p6lx Container image "appscode/voyager:v13.0.0-rc.0" already present on machine
2m7s Warning AdmissionWebhookNotActivated deployment/voyager-release50-huha timed out waiting for the condition
99s Warning BackOff pod/voyager-release50-huha-7f46b9fb6f-9p6lx Back-off restarting failed container

from voyager.

Hello, We have released https://blog.byte.builders/post/voyager-v2021.09.15/ . Can you please check if this works with cri-o?

from voyager.