apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-25T11:20:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-169-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-169.ec2.internal uid: 4e56613f-401e-4f75-b988-0fc807231f4a resourceVersion: "18313" uid: 5d9b2f60-54d6-47fe-845f-3d4a123aa8be spec: sourcePod: network-check-source-7f44b6dd87-9ssn4 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-05-25T11:27:22Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.138874ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T11:34:22Z" - latency: 976.403µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T11:33:22Z" - latency: 1.004558ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T11:32:22Z" - latency: 955.181µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T11:31:22Z" - latency: 1.307797ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T11:30:22Z" - latency: 981.798µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T11:29:22Z" - latency: 967.427µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T11:28:22Z" - latency: 991.954µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T11:27:22Z" - latency: 971.956µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T11:26:22Z" - latency: 892.559µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T11:25:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-25T11:20:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-169-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-169.ec2.internal uid: 4e56613f-401e-4f75-b988-0fc807231f4a resourceVersion: "20360" uid: 65c7c4e6-372f-4920-86c2-e0943fc8264f spec: sourcePod: network-check-source-7f44b6dd87-9ssn4 targetEndpoint: a6224edd928c340299054178dae62fca-b075b73004ece036.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-25T11:26:22Z" message: 'load-balancer-api-external: tcp connection to a6224edd928c340299054178dae62fca-b075b73004ece036.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.607724ms message: 'load-balancer-api-external: tcp connection to a6224edd928c340299054178dae62fca-b075b73004ece036.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T11:38:22Z" - latency: 7.094316ms message: 'load-balancer-api-external: resolved host name a6224edd928c340299054178dae62fca-b075b73004ece036.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T11:38:22Z" - latency: 4.098126ms message: 'load-balancer-api-external: tcp connection to a6224edd928c340299054178dae62fca-b075b73004ece036.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T11:37:22Z" - latency: 9.90226ms message: 'load-balancer-api-external: resolved host name a6224edd928c340299054178dae62fca-b075b73004ece036.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T11:37:22Z" - latency: 4.247696ms message: 'load-balancer-api-external: tcp connection to a6224edd928c340299054178dae62fca-b075b73004ece036.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T11:36:22Z" - latency: 6.235089ms message: 'load-balancer-api-external: resolved host name a6224edd928c340299054178dae62fca-b075b73004ece036.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T11:36:22Z" - latency: 4.795897ms message: 'load-balancer-api-external: tcp connection to a6224edd928c340299054178dae62fca-b075b73004ece036.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T11:35:22Z" - latency: 6.796007ms message: 'load-balancer-api-external: resolved host name a6224edd928c340299054178dae62fca-b075b73004ece036.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T11:35:22Z" - latency: 5.30511ms message: 'load-balancer-api-external: tcp connection to a6224edd928c340299054178dae62fca-b075b73004ece036.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T11:34:22Z" - latency: 6.35459ms message: 'load-balancer-api-external: resolved host name a6224edd928c340299054178dae62fca-b075b73004ece036.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T11:34:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-25T11:20:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-169-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-169.ec2.internal uid: 4e56613f-401e-4f75-b988-0fc807231f4a resourceVersion: "20361" uid: 62f79f61-c690-4822-81c6-69f8e3d59ac6 spec: sourcePod: network-check-source-7f44b6dd87-9ssn4 targetEndpoint: a6224edd928c340299054178dae62fca-b075b73004ece036.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-25T11:26:22Z" message: 'load-balancer-api-internal: tcp connection to a6224edd928c340299054178dae62fca-b075b73004ece036.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.635187ms message: 'load-balancer-api-internal: tcp connection to a6224edd928c340299054178dae62fca-b075b73004ece036.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T11:38:22Z" - latency: 7.050878ms message: 'load-balancer-api-internal: resolved host name a6224edd928c340299054178dae62fca-b075b73004ece036.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T11:38:22Z" - latency: 4.636837ms message: 'load-balancer-api-internal: tcp connection to a6224edd928c340299054178dae62fca-b075b73004ece036.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T11:37:22Z" - latency: 9.818707ms message: 'load-balancer-api-internal: resolved host name a6224edd928c340299054178dae62fca-b075b73004ece036.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T11:37:22Z" - latency: 4.275845ms message: 'load-balancer-api-internal: tcp connection to a6224edd928c340299054178dae62fca-b075b73004ece036.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T11:36:22Z" - latency: 6.20786ms message: 'load-balancer-api-internal: resolved host name a6224edd928c340299054178dae62fca-b075b73004ece036.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T11:36:22Z" - latency: 4.804105ms message: 'load-balancer-api-internal: tcp connection to a6224edd928c340299054178dae62fca-b075b73004ece036.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T11:35:22Z" - latency: 6.782191ms message: 'load-balancer-api-internal: resolved host name a6224edd928c340299054178dae62fca-b075b73004ece036.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T11:35:22Z" - latency: 5.240768ms message: 'load-balancer-api-internal: tcp connection to a6224edd928c340299054178dae62fca-b075b73004ece036.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T11:34:22Z" - latency: 6.426472ms message: 'load-balancer-api-internal: resolved host name a6224edd928c340299054178dae62fca-b075b73004ece036.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T11:34:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-25T11:20:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-169-to-network-check-target-ip-10-0-128-161 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-169.ec2.internal uid: 4e56613f-401e-4f75-b988-0fc807231f4a resourceVersion: "18310" uid: a8a2fad0-2af3-43d1-9e46-6dd96e155e6e spec: sourcePod: network-check-source-7f44b6dd87-9ssn4 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-25T11:27:22Z" message: 'network-check-target-ip-10-0-128-161: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.678219ms message: 'network-check-target-ip-10-0-128-161: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T11:34:22Z" - latency: 1.481978ms message: 'network-check-target-ip-10-0-128-161: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T11:33:22Z" - latency: 1.842539ms message: 'network-check-target-ip-10-0-128-161: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T11:32:22Z" - latency: 1.839644ms message: 'network-check-target-ip-10-0-128-161: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T11:31:22Z" - latency: 1.871225ms message: 'network-check-target-ip-10-0-128-161: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T11:30:22Z" - latency: 1.646276ms message: 'network-check-target-ip-10-0-128-161: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T11:29:22Z" - latency: 1.9007ms message: 'network-check-target-ip-10-0-128-161: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T11:28:22Z" - latency: 1.848751ms message: 'network-check-target-ip-10-0-128-161: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T11:27:22Z" - latency: 1.683086ms message: 'network-check-target-ip-10-0-128-161: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T11:26:22Z" - latency: 1.734965ms message: 'network-check-target-ip-10-0-128-161: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T11:25:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-25T11:20:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-169-to-network-check-target-ip-10-0-130-103 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-169.ec2.internal uid: 4e56613f-401e-4f75-b988-0fc807231f4a resourceVersion: "18311" uid: 39cae4d5-22c0-4afe-bf8e-69cd67bd816b spec: sourcePod: network-check-source-7f44b6dd87-9ssn4 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-25T11:27:22Z" message: 'network-check-target-ip-10-0-130-103: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.978996ms message: 'network-check-target-ip-10-0-130-103: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T11:34:22Z" - latency: 2.079104ms message: 'network-check-target-ip-10-0-130-103: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T11:33:22Z" - latency: 2.044732ms message: 'network-check-target-ip-10-0-130-103: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T11:32:22Z" - latency: 2.029927ms message: 'network-check-target-ip-10-0-130-103: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T11:31:22Z" - latency: 2.369057ms message: 'network-check-target-ip-10-0-130-103: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T11:30:22Z" - latency: 2.056205ms message: 'network-check-target-ip-10-0-130-103: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T11:29:22Z" - latency: 2.247898ms message: 'network-check-target-ip-10-0-130-103: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T11:28:22Z" - latency: 2.30267ms message: 'network-check-target-ip-10-0-130-103: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T11:27:22Z" - latency: 2.044908ms message: 'network-check-target-ip-10-0-130-103: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T11:26:22Z" - latency: 2.035029ms message: 'network-check-target-ip-10-0-130-103: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T11:25:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-25T11:20:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-169-to-network-check-target-ip-10-0-139-169 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-169.ec2.internal uid: 4e56613f-401e-4f75-b988-0fc807231f4a resourceVersion: "18312" uid: 3e53f74f-4e66-4cb2-b5ca-84327ce0a223 spec: sourcePod: network-check-source-7f44b6dd87-9ssn4 targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-25T11:27:22Z" message: 'network-check-target-ip-10-0-139-169: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 865.727µs message: 'network-check-target-ip-10-0-139-169: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T11:34:22Z" - latency: 943.514µs message: 'network-check-target-ip-10-0-139-169: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T11:33:22Z" - latency: 933.523µs message: 'network-check-target-ip-10-0-139-169: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T11:32:22Z" - latency: 1.31715ms message: 'network-check-target-ip-10-0-139-169: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T11:31:22Z" - latency: 748.401µs message: 'network-check-target-ip-10-0-139-169: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T11:30:22Z" - latency: 870.353µs message: 'network-check-target-ip-10-0-139-169: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T11:29:22Z" - latency: 851.484µs message: 'network-check-target-ip-10-0-139-169: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T11:28:22Z" - latency: 1.212207ms message: 'network-check-target-ip-10-0-139-169: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T11:27:22Z" - latency: 871.608µs message: 'network-check-target-ip-10-0-139-169: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T11:26:22Z" - latency: 888.389µs message: 'network-check-target-ip-10-0-139-169: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T11:25:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-25T11:20:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-169-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-169.ec2.internal uid: 4e56613f-401e-4f75-b988-0fc807231f4a resourceVersion: "20359" uid: 4157f9c3-9e20-4017-99f5-bac676c2c1c6 spec: sourcePod: network-check-source-7f44b6dd87-9ssn4 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-05-25T11:26:22Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 885.277µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-25T11:38:22Z" - latency: 2.072219ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-25T11:38:22Z" - latency: 819.83µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-25T11:37:22Z" - latency: 1.611704ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-25T11:37:22Z" - latency: 825.284µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-25T11:36:22Z" - latency: 1.871033ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-25T11:36:22Z" - latency: 796.921µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-25T11:35:22Z" - latency: 1.699111ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-25T11:35:22Z" - latency: 834.986µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-25T11:34:22Z" - latency: 1.788243ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-25T11:34:22Z" kind: List metadata: resourceVersion: ""