It doesn’t allow me to do this because i used it as operator.
Yesterday i checked this but it didn’t work for me, it seem i installed as operator and it doesn;t allow to apply on pods. Let me try today again. Any simple solutions to integrate pods with certs?
Can you check if other application pods are able to reach the endpoints. Installing via operator should not make any difference, the pods should be able to reach out. What version of K8’s are you using? Also, I see you only have 2 nodes in the cluster, for quorum you should have odd number of nodes.
v1.18.3 my kubernetes version,
This morning i added additional 2 nodes but my pod cannot initialize on them. It say : Readiness probe failed: HTTP probe failed with statuscode: 503
v1.18.3 my kubernetes version,
This morning i added additional 2 nodes but my pod cannot initialize on them. It say : Readiness probe failed: HTTP probe failed with statuscode: 503
also i found that when secure boot is enabled pods are not provision to nodes. It is possible to skip this because i don;t have such option in VM
kubenode5 cde2dfd3-d11c-467f-be71-5f21941563a1 Initializing 2.6.1.6-3409af2 98m
[root@kubenode1 ~]# kubectl get storagenodes -n kube-system -l name=portworx -o wide
NAME ID STATUS VERSION AGE
kubenode2 4e4f6c33-3123-4aef-9557-964e9af9a31d Offline 2.6.1.6-3409af2 2d18h
kubenode3 875b7576-c140-4ea1-b919-66532c6b539c NotInQuorum 2.6.1.6-3409af2 2d18h
kubenode4 0a416754-c7be-496a-8184-2846bdd435b1 Initializing 2.6.1.6-3409af2 112m
kubenode5 cde2dfd3-d11c-467f-be71-5f21941563a1 Initializing 2.6.1.6-3409af2 98m
I have one question, Can you please explain why when i do get storage nodes it shows Initializing status on kubenode4 and kubenode5. But when i do describe of those storagenodes it shows status ONLINE
[root@kubenode1 ~]# kubectl get storagenodes -n kube-system -l name=portworx -o wide
NAME ID STATUS VERSION AGE
kubenode2 4e4f6c33-3123-4aef-9557-964e9af9a31d Online 2.6.1.6-3409af2 5d21h
kubenode3 875b7576-c140-4ea1-b919-66532c6b539c Online 2.6.1.6-3409af2 5d21h
kubenode4 0a416754-c7be-496a-8184-2846bdd435b1 Initializing 2.6.1.6-3409af2 3d4h
kubenode5 cde2dfd3-d11c-467f-be71-5f21941563a1 Initializing 2.6.1.6-3409af2 3d2h
[root@kubenode1 ~]# kubectl describe storagenodes.core.libopenstorage.org -n kube-system kubenode5
Name: kubenode5
Namespace: kube-system
Labels: name=portworx
Annotations:
API Version: core.libopenstorage.org/v1
Kind: StorageNode
Metadata:
Creation Timestamp: 2020-12-11T08:29:36Z
Generation: 3
Managed Fields:
API Version: core.libopenstorage.org/v1
Fields Type: FieldsV1
fieldsV1:
f:status:
f:conditions:
f:phase:
f:storage:
.:
f:totalSize:
f:usedSize:
Manager: operator
Operation: Update
Time: 2020-12-11T08:34:51Z
Owner References:
API Version: core.libopenstorage.org/v1
Block Owner Deletion: true
Controller: true
Kind: StorageCluster
Name: px-cluster-fc58ace4-2bc4-42c7-a82e-3ef03e49b70d
UID: 224fac77-b5e4-43b9-85df-0c78fd2c7d4d
Resource Version: 81093682
Self Link: /apis/core.libopenstorage.org/v1/namespaces/kube-system/storagenodes/kubenode5
UID: 99e53930-fae4-42c0-8799-9f32423f6450
Spec:
Cloud Storage:
Version: 2.6.1.6-3409af2
Status:
Conditions:
Last Transition Time: 2020-12-11T08:34:51Z
Status: Online
Type: NodeState
Last Transition Time: 2020-12-11T08:41:04Z
Message: PX is ready on this node
Reason: NodeStartSuccess
Status: Succeeded
Type: NodeInit
Geography:
Network:
Data IP: 192.168.1.138
Mgmt IP: 192.168.1.138
Node UID: cde2dfd3-d11c-467f-be71-5f21941563a1
Phase: Initializing
Storage:
Total Size: 10Gi
Used Size: 1363652116
Events:
[root@kubenode1 ~]#
Hi,
I have signed up for the 30 days free trial and am experiencing the same issue. I generated the specs using central and deployed both the portworx enterprise and portoworx backup but my cluster doesn’t appear in PX-Central.
When I run the commands that were shared in the thread, I am getting the following responses.
[root@ip-10-10-33-64 /]# curl https://pxessentials.portworx.com/osb/ping
{"status":"pong","message":"PX-OSB is UP and running"}
/opt/pwx/bin/pxctl status
Status: PX is operational
License: Trial (expires in 30 days)
Node ID: 60f0efa0-7148-4eaa-9c6b-6d79263234ae
IP: 10.10.33.64
Local Storage Pool: 1 pool
POOL IO_PRIORITY RAID_LEVEL USABLE USED STATUS ZONE REGION
0 HIGH raid0 150 GiB 7.7 GiB Online eu-west-1a eu-west-1
Local Storage Devices: 1 device
Device Path Media Type Size Last-Scan
0:1 /dev/nvme2n1 STORAGE_MEDIUM_NVME 150 GiB 15 Jan 21 04:48 UTC
total - 150 GiB
Cache Devices:
* No cache devices
Cluster Summary
Cluster ID: px-cluster-a9b7ba1c-4602-40d7-be04-4afcb0a6a5e9
Cluster UUID: a8949f94-795a-4597-865f-2a942bf89c1d
Scheduler: kubernetes
Nodes: 5 node(s) with storage (5 online), 1 node(s) without storage (1 online)
IP ID SchedulerNodeName StorageNode Used Capacity Status StorageStatus Version Kernel OS
10.10.127.82 c253ffc6-5ce2-4e2a-9179-443ca0c4600e ip-10-10-127-82.eu-west-1.compute.internal Yes 7.7 GiB 150 GiB Online Up 2.6.2.1-4c79af9 5.4.0-1029-aws Ubuntu 20.04.1 LTS
10.10.79.89 9b16c392-dc3a-4f44-91a5-e3de063bc6c6 ip-10-10-79-89.eu-west-1.compute.internal Yes 7.7 GiB 150 GiB Online Up 2.6.2.1-4c79af9 5.4.0-1029-aws Ubuntu 20.04.1 LTS
10.10.33.64 60f0efa0-7148-4eaa-9c6b-6d79263234ae ip-10-10-33-64.eu-west-1.compute.internal Yes 7.7 GiB 150 GiB Online Up (This node) 2.6.2.1-4c79af9 5.4.0-1029-aws Ubuntu 20.04.1 LTS
10.10.77.52 55485509-9b28-4fb4-8075-f367750ab6ca ip-10-10-77-52.eu-west-1.compute.internal Yes 7.7 GiB 150 GiB Online Up 2.6.2.1-4c79af9 5.4.0-1029-aws Ubuntu 20.04.1 LTS
10.10.105.179 48aee6fb-093d-4b77-8981-d31aba7b64a3 ip-10-10-105-179.eu-west-1.compute.internal Yes 7.7 GiB 150 GiB Online Up 2.6.2.1-4c79af9 5.4.0-1029-aws Ubuntu 20.04.1 LTS
10.10.32.248 d6e55aef-36b0-4129-b68c-5817b9e6b998 ip-10-10-32-248.eu-west-1.compute.internal No 0 B 0 B Online No Storage 2.6.2.1-4c79af9 5.4.0-1029-aws Ubuntu 20.04.1 LTS
Global Storage Pool
Total Used : 38 GiB
Total Capacity : 750 GiB
I also noticed that a service object has been created of type LB in the px-backup namespace that only works on port 80. Is there a way to change that to 443 and use HTTPS. I also don’t know how to login to that portal, when deploying I had not selected the OIDC option.
Any help will be highly appreciated, as I really want to get to understand portworx before the end of the trial period to decide if this fulfils all our requirements or not, so we can decide if we should pay the license fee or not.
Thanks,
Hi @Mohammad_Ayub
I see that you are using the 30 day trial for Portworx enterprise, not Portworx essential.
What is the use case you are trying to test? Is it PX-Backup or Portworx Enterprise?
Tapas
I installed as an operator some time ago and everything worked for me as usual