-
Notifications
You must be signed in to change notification settings - Fork 131
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
Alien Pods are not appearing. #93
Comments
Dear @javajon Thnk you for opening an issue. Can you please try Thank you, |
@javajon I also added the guide for installing using NodePort Service with no TLS. Please let me know if it is your case |
Tried that, no improvement. The aliens are still ghosting me as shown in image above.😉 Here was the installation process, following your suggestion. Once it is running I can get to the UI via public url https://learning.oreilly.com/interactive-lab/~/9781492083924/lab/. Notice that this public URL is the specific O'Reilly lab instance with the node port baked into the URL. The labs route this URL to the K8s service nodeport. Notice the log output produces non-uniform characters. $ helm repo add kubeinvaders https://lucky-sideburn.github.io/helm-charts/ && helm repo list
"kubeinvaders" has been added to your repositories
NAME URL
kubernetes-dashboard https://kubernetes.github.io/dashboard/
metrics-server https://kubernetes-sigs.github.io/metrics-server/
kubelet-csr-approver https://postfinance.github.io/kubelet-csr-approver/
rimusz https://charts.rimusz.net
kubeinvaders https://lucky-sideburn.github.io/helm-charts/
$ VERSION=1.9.7
$ helm install kubeinvaders kubeinvaders/kubeinvaders \
> --version=$VERSION \
> --namespace kubeinvaders \
> --create-namespace \
> --set service.type=NodePort \
> --set service.nodePort=30016 \
> --set ingress.enabled=false \
> --set config.target_namespace="default\,more-apps" \
> --set route_host=2886748165-30016-host11nc.environments.katacoda.com:80
W0221 19:03:02.444077 51988 warnings.go:70] unknown field "rules"
NAME: kubeinvaders
LAST DEPLOYED: Fri Feb 21 19:03:01 2025
NAMESPACE: kubeinvaders
STATUS: deployed
REVISION: 1
NOTES:
Thank you for installing KubeInvaders!
$ kubectl set env deployment/kubeinvaders DISABLE_TLS=true -n kubeinvaders
deployment.apps/kubeinvaders env updated
$ k get namespaces
NAME STATUS AGE
default Active 163m
kube-flannel Active 162m
kube-node-lease Active 163m
kube-public Active 163m
kube-system Active 163m
kubeinvaders Active 3m31s
kubernetes-dashboard Active 12m
$ k get all -n kubeinvaders
NAME READY STATUS RESTARTS AGE
pod/kubeinvaders-c9c875cc4-htvqs 1/1 Running 0 8m52s
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
service/kubeinvaders NodePort 10.104.18.119 <none> 80:30016/TCP 9m2s
NAME READY UP-TO-DATE AVAILABLE AGE
deployment.apps/kubeinvaders 1/1 1 1 9m2s
NAME DESIRED CURRENT READY AGE
replicaset.apps/kubeinvaders-7cfbdd986f 0 0 0 9m2s
replicaset.apps/kubeinvaders-c9c875cc4 1 1 1 8m52s
$ k logs -n kubeinvaders kubeinvaders-c9c875cc4-htvqs
2025/02/21 19:03:30 [notice] 59#59: using the "epoll" event method
2025/02/21 19:03:30 [notice] 59#59: openresty/1.27.1.1
2025/02/21 19:03:30 [notice] 59#59: OS: Linux 6.8.0-53-generic
2025/02/21 19:03:30 [notice] 59#59: getrlimit(RLIMIT_NOFILE): 1048576:1048576
2025/02/21 19:03:30 [notice] 59#59: start worker processes
2025/02/21 19:03:30 [notice] 59#59: start worker process 69
2025/02/21 19:03:30 [notice] 59#59: start worker process 70
2025/02/21 19:03:38 [info] 69#69: *1 client sent invalid method while reading client request line, client: 10.244.0.0, server: , request: "���c��1�����Z:��L��::�2?�1;"
2025/02/21 19:03:39 [info] 69#69: *3 client sent invalid method while reading client request line, client: 10.244.0.0, server: , request: "��.�^��8d�̻M<��)"�x{���v�A\E��L� !�Ie݈�`��F+ڌ#�$���Y�R�kf���&�+�/�,�0̨̩� ��"
2025/02/21 19:03:39 [info] 69#69: *4 client sent invalid method while reading client request line, client: 10.244.0.0, server: , request: "��9Ѓ:����S�����T�C�����S��0 �� U�+��ϗG�^.��y�"
2025/02/21 19:03:39 [info] 69#69: *7 client sent invalid method while reading client request line, client: 10.244.0.0, server: , request: "��m���,��ce���)ؙ-m>���m�� ?�U�ۉ1�5%#����A"
2025/02/21 19:03:39 [info] 69#69: *8 client sent invalid method while reading client request line, client: 10.244.0.0, server: , request: "��M�� �z:{f�%��VK(���fGEL�l� IZ��ҰQ�A�Rk��@m�.�q�[�%ڦ�&�+�/�,�0̨̩� ��"
2025/02/21 19:03:39 [info] 69#69: *9 client sent invalid method while reading client request line, client: 10.244.0.0, server: , request: "����x��:���A�H�{����*%s/<=� T+�w)�!�`�m�UY�u}^����?�e���8&�+�/�,�0̨̩� ��"
2025/02/21 19:03:39 [info] 70#70: *10 client sent invalid method while reading client request line, client: 10.244.0.0, server: , request: "����%|�E�/["�|]N�x��x������R g�Q�9���~{Q��9��b��ɷ�I���m�~&�+�/�,�0̨̩� ��"
2025/02/21 19:03:39 [info] 70#70: *11 client sent invalid method while reading client request line, client: 10.244.0.0, server: , request: "��toZ~A0"
2025/02/21 19:03:39 [info] 69#69: *12 client sent invalid method while reading client request line, client: 10.244.0.0, server: , request: "��q��^��1}"u1,P�!�@
5��۳�.u� "�
��r��?��x��wNO�w��zM��&�+�/�,�0̨̩� ��"
2025/02/21 19:03:39 [info] 69#69: *13 client sent invalid method while reading client request line, client: 10.244.0.0, server: , request: "��:�L�`-1)��l��j���e��Q�'ɓh�� ��z:�ð���Mg�hC�ߡŶ�B����&�+�/�,�0̨̩� ��"
2025/02/21 19:03:39 [info] 69#69: *14 client sent invalid method while reading client request line, client: 10.244.0.0, server: , request: "���B���9V�b����
�?�s"
2025/02/21 19:03:39 [info] 69#69: *15 client sent invalid method while reading client request line, client: 10.244.0.0, server: , request: "��;W�&��
P&��]�M�
?����7]� ��̏90U���3v��4
�������&�+�/�,�0̨̩� ��"
2025/02/21 19:03:39 [info] 70#70: *16 client sent invalid method while reading client request line, client: 10.244.0.0, server: , request: "��]O���rx�ЅkȊY�a��Ŵ��}.�"�
�H �@�k�a�8��b<n�)��"
2025/02/21 19:03:39 [info] 69#69: *17 client sent invalid method while reading client request line, client: 10.244.0.0, server: , request: "��̱�
y���N��T��g�a���g���J` �%�ꩯ݆�_�1�ma/�d6;���X��&�+�/�,�0̨̩� ��"
2025/02/21 19:03:39 [info] 69#69: *18 client sent invalid method while reading client request line, client: 10.244.0.0, server: , request: "���Gƥ��`�
�r�Aޔ�$��T��mdw"
2025/02/21 19:03:39 [info] 69#69: *20 client sent invalid method while reading client request line, client: 10.244.0.0, server: , request: "����~t_g�?�a�d+N3�"
2025/02/21 19:03:39 [info] 69#69: *21 client sent invalid method while reading client request line, client: 10.244.0.0, server: , request: "���r���Nq��h�,��/��@rPI_��B\1S7� ��r��[�<J����F�evg'��PM�-��&�+�/�,�0̨̩� ��"
2025/02/21 19:03:39 [info] 70#70: *23 client sent invalid method while reading client request line, client: 10.244.0.0, server: , request: "��2�U'�R�~�Y&����o\T��/6�a�~��% n��Ҡ#�D�cjǚ�~2PS<W)��}��ՊLH&�+�/�,�0̨̩� ��"
2025/02/21 19:03:39 [info] 70#70: *22 client sent invalid method while reading client request line, client: 10.244.0.0, server: , request: "�����"
2025/02/21 19:03:39 [info] 69#69: *25 client sent invalid method while reading client request line, client: 10.244.0.0, server: , request: "��!&q1�
��j"
2025/02/21 19:03:39 [info] 70#70: *27 client sent invalid method while reading client request line, client: 10.244.0.0, server: , request: "����w�=�2��hlO8�)�<v�B(��M ����ٽ�^\��:上}O�
���~�
N|e�b&�+�/�,�0̨̩� ��"
2025/02/21 19:03:39 [info] 70#70: *28 client sent invalid method while reading client request line, client: 10.244.0.0, server: , request: "��ͣ}_�����)l��EP��$����*ll� BX ؟�ΐr����vս�5"܇�����O^��\���&�+�/�,�0̨̩� ��"
2025/02/21 19:03:40 [info] 70#70: *29 client sent invalid method while reading client request line, client: 10.244.0.0, server: , request: "���rzׂ�Yv
ҷ��&��
��Pgp��b���#� ���tz���#/�$�|�$)��r�i�.�8&�+�/�,�0̨̩� ��"
2025/02/21 19:03:40 [info] 70#70: *30 client sent invalid method while reading client request line, client: 10.244.0.0, server: , request: "���J�Ƥ��V[��oI]��@�� m���"
2025/02/21 19:03:58 [info] 70#70: *31 client sent invalid method while reading client request line, client: 10.244.0.0, server: , request: "���>�U4XS+��C�g�i��of>3P�ՏK?/ x��:c�}�ΰ��m&/�`�6cX�,��4�'X��&�+�/�,�0̨̩� ��"
2025/02/21 19:03:59 [info] 70#70: *32 client sent invalid method while reading client request line, client: 10.244.0.0, server: , request: "��C�ʁ�� ����f��4��O�N觐Y)�ي �¥r�Aٕ�p��_���x'��K}1�<<�|��Q&�+�/�,�0̨̩� ��"
2025/02/21 19:04:08 [info] 70#70: *33 client sent invalid method while reading client request line, client: 10.244.0.0, server: , request: "��"
2025/02/21 19:04:13 [info] 70#70: *34 client sent invalid method while reading client request line, client: 10.244.0.0, server: , request: "��(
����/3�蜁�V�O�I��T�<�$�s<j� ��G�nUK�C�$��H�����Ԁ��&�+�/�,�0̨̩� ��"
2025/02/21 19:04:36 [info] 70#70: *35 client sent invalid method while reading client request line, client: 10.244.0.0, server: , request: "��-�Іą���L�q�ɓ�⿶��� B���xu�Z��D��^�g�ӌ{��-x�&�+�/�,�0̨̩� ��"
2025/02/21 19:04:39 [info] 70#70: *24 client timed out (110: Connection timed out) while waiting for request, client: 10.244.0.0, server: 0.0.0.0:8080
2025/02/21 19:04:47 [info] 69#69: *37 client sent invalid method while reading client request line, client: 10.244.0.0, server: , request: "���3t��4e@�M"
2025/02/21 19:04:57 [info] 69#69: *39 client sent invalid method while reading client request line, client: 10.244.0.0, server: , request: "��0�Έ��c;�>�
v}�>_�Bγ(�J �eu���l*e���^j�nˬ��P|����w&�+�/�,�0̨̩� ��"
2025/02/21 19:05:08 [info] 69#69: *41 client sent invalid method while reading client request line, client: 10.244.0.0, server: , request: "��|Oǡ��ܛC�zf�|�r��
6ƙkOj� $���"
2025/02/21 19:05:21 [info] 69#69: *42 client sent invalid method while reading client request line, client: 10.244.0.0, server: , request: "���mZ�,{qs�
�Sz�g�v�]LO�87�� ��d*��Ő�����=,���u�Oh��s�Ɩe8�&�+�/�,�0̨̩� ��"
2025/02/21 19:05:31 [info] 69#69: *44 client sent invalid method while reading client request line, client: 10.244.0.0, server: , request: "�����|+z��֬|t��?h�$GJ�G�,Vx |S�;.4����w.|CJ���5�VmaPG���&�+�/�,�0̨̩� ��" Can I suggest a requirement to enter a bearer token to access the UI? Have the user (or chart) create an account, assign it to the cluster admin role, then create a secret assigned to the account. Get the bear token from the secret. I have a formula for this with the kuberetes dashboard as well as a lab that demonstrates kubeapps secure access. I would be happy to share that recommended setup. Feel free to set up a support call to diagnose live. |
Installed with
Have these pods running:
In the UI the firing ship appears but no alien pods appears.
Here is the export of the setting.json
Oddly, the UI reads:
Selected Namespace: NULL
Deleted Pods Total: 0
Chaos Jobs Total: 0
Current Chaos Pods: 0
Not Running Pods: 0
Current Replicas State Delay: 0 sec
Latest Replicas State Delay: 0 sec
and the UI reports "Current Namespace: undefined".
The "n" key does nothing.
The text was updated successfully, but these errors were encountered: