apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T15:55:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-171-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-171.ec2.internal uid: a15f2cbd-1808-4363-8bba-707552796bd5 resourceVersion: "71265" uid: 34e553a0-ec28-4c62-9e10-21062c14778a spec: sourcePod: network-check-source-7d88cb55d8-2tgtj targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-27T16:02:17Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 784.291µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T16:44:17Z" - latency: 1.030121ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T16:43:17Z" - latency: 894.329µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T16:42:17Z" - latency: 878.159µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T16:41:17Z" - latency: 1.271586ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T16:40:17Z" - latency: 1.24276ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T16:39:17Z" - latency: 939.649µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T16:38:17Z" - latency: 1.075848ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T16:37:17Z" - latency: 1.198456ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T16:36:17Z" - latency: 1.304118ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T16:35:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T15:55:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-171-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-171.ec2.internal uid: a15f2cbd-1808-4363-8bba-707552796bd5 resourceVersion: "70438" uid: b0fe8b19-49c8-47c6-ba70-9a38e5dc5441 spec: sourcePod: network-check-source-7d88cb55d8-2tgtj targetEndpoint: aaceb46e3dfdf41d588334da8c4f8c53-c3efe3f5d5230e67.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-27T16:01:17Z" message: 'load-balancer-api-external: tcp connection to aaceb46e3dfdf41d588334da8c4f8c53-c3efe3f5d5230e67.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.933576ms message: 'load-balancer-api-external: tcp connection to aaceb46e3dfdf41d588334da8c4f8c53-c3efe3f5d5230e67.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T16:43:17Z" - latency: 6.706786ms message: 'load-balancer-api-external: resolved host name aaceb46e3dfdf41d588334da8c4f8c53-c3efe3f5d5230e67.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T16:43:17Z" - latency: 4.496839ms message: 'load-balancer-api-external: tcp connection to aaceb46e3dfdf41d588334da8c4f8c53-c3efe3f5d5230e67.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T16:42:17Z" - latency: 6.774957ms message: 'load-balancer-api-external: resolved host name aaceb46e3dfdf41d588334da8c4f8c53-c3efe3f5d5230e67.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T16:42:17Z" - latency: 4.770197ms message: 'load-balancer-api-external: tcp connection to aaceb46e3dfdf41d588334da8c4f8c53-c3efe3f5d5230e67.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T16:41:17Z" - latency: 6.874942ms message: 'load-balancer-api-external: resolved host name aaceb46e3dfdf41d588334da8c4f8c53-c3efe3f5d5230e67.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T16:41:17Z" - latency: 6.236383ms message: 'load-balancer-api-external: tcp connection to aaceb46e3dfdf41d588334da8c4f8c53-c3efe3f5d5230e67.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T16:40:17Z" - latency: 7.073774ms message: 'load-balancer-api-external: resolved host name aaceb46e3dfdf41d588334da8c4f8c53-c3efe3f5d5230e67.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T16:40:17Z" - latency: 3.871783ms message: 'load-balancer-api-external: tcp connection to aaceb46e3dfdf41d588334da8c4f8c53-c3efe3f5d5230e67.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T16:39:17Z" - latency: 6.582162ms message: 'load-balancer-api-external: resolved host name aaceb46e3dfdf41d588334da8c4f8c53-c3efe3f5d5230e67.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T16:39:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T15:55:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-171-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-171.ec2.internal uid: a15f2cbd-1808-4363-8bba-707552796bd5 resourceVersion: "70439" uid: 14ce43ff-9fbe-45a6-9024-6cc55ddbba45 spec: sourcePod: network-check-source-7d88cb55d8-2tgtj targetEndpoint: aaceb46e3dfdf41d588334da8c4f8c53-c3efe3f5d5230e67.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-27T16:01:17Z" message: 'load-balancer-api-internal: tcp connection to aaceb46e3dfdf41d588334da8c4f8c53-c3efe3f5d5230e67.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.947928ms message: 'load-balancer-api-internal: tcp connection to aaceb46e3dfdf41d588334da8c4f8c53-c3efe3f5d5230e67.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T16:43:17Z" - latency: 6.629279ms message: 'load-balancer-api-internal: resolved host name aaceb46e3dfdf41d588334da8c4f8c53-c3efe3f5d5230e67.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T16:43:17Z" - latency: 4.626747ms message: 'load-balancer-api-internal: tcp connection to aaceb46e3dfdf41d588334da8c4f8c53-c3efe3f5d5230e67.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T16:42:17Z" - latency: 6.7132ms message: 'load-balancer-api-internal: resolved host name aaceb46e3dfdf41d588334da8c4f8c53-c3efe3f5d5230e67.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T16:42:17Z" - latency: 4.801395ms message: 'load-balancer-api-internal: tcp connection to aaceb46e3dfdf41d588334da8c4f8c53-c3efe3f5d5230e67.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T16:41:17Z" - latency: 6.829062ms message: 'load-balancer-api-internal: resolved host name aaceb46e3dfdf41d588334da8c4f8c53-c3efe3f5d5230e67.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T16:41:17Z" - latency: 4.800301ms message: 'load-balancer-api-internal: tcp connection to aaceb46e3dfdf41d588334da8c4f8c53-c3efe3f5d5230e67.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T16:40:17Z" - latency: 6.981746ms message: 'load-balancer-api-internal: resolved host name aaceb46e3dfdf41d588334da8c4f8c53-c3efe3f5d5230e67.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T16:40:17Z" - latency: 3.929267ms message: 'load-balancer-api-internal: tcp connection to aaceb46e3dfdf41d588334da8c4f8c53-c3efe3f5d5230e67.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T16:39:17Z" - latency: 6.52087ms message: 'load-balancer-api-internal: resolved host name aaceb46e3dfdf41d588334da8c4f8c53-c3efe3f5d5230e67.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T16:39:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T15:55:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-171-to-network-check-target-ip-10-0-135-171 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-171.ec2.internal uid: a15f2cbd-1808-4363-8bba-707552796bd5 resourceVersion: "71262" uid: 418151c8-d12b-431b-a19c-10234b3a0a96 spec: sourcePod: network-check-source-7d88cb55d8-2tgtj targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-27T16:02:17Z" message: 'network-check-target-ip-10-0-135-171: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.272779ms message: 'network-check-target-ip-10-0-135-171: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T16:44:17Z" - latency: 1.082464ms message: 'network-check-target-ip-10-0-135-171: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T16:43:17Z" - latency: 1.475359ms message: 'network-check-target-ip-10-0-135-171: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T16:42:17Z" - latency: 1.802943ms message: 'network-check-target-ip-10-0-135-171: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T16:41:17Z" - latency: 1.408466ms message: 'network-check-target-ip-10-0-135-171: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T16:40:17Z" - latency: 860.645µs message: 'network-check-target-ip-10-0-135-171: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T16:39:17Z" - latency: 1.540491ms message: 'network-check-target-ip-10-0-135-171: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T16:38:17Z" - latency: 929.361µs message: 'network-check-target-ip-10-0-135-171: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T16:37:17Z" - latency: 1.070949ms message: 'network-check-target-ip-10-0-135-171: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T16:36:17Z" - latency: 1.35493ms message: 'network-check-target-ip-10-0-135-171: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T16:35:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T15:55:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-171-to-network-check-target-ip-10-0-141-100 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-171.ec2.internal uid: a15f2cbd-1808-4363-8bba-707552796bd5 resourceVersion: "71264" uid: 9df4dc4a-1f67-4afc-9ca6-67dc0039a571 spec: sourcePod: network-check-source-7d88cb55d8-2tgtj targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-27T16:02:17Z" message: 'network-check-target-ip-10-0-141-100: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.069571ms message: 'network-check-target-ip-10-0-141-100: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T16:44:17Z" - latency: 2.186184ms message: 'network-check-target-ip-10-0-141-100: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T16:43:17Z" - latency: 2.380265ms message: 'network-check-target-ip-10-0-141-100: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T16:42:17Z" - latency: 2.445833ms message: 'network-check-target-ip-10-0-141-100: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T16:41:17Z" - latency: 2.228823ms message: 'network-check-target-ip-10-0-141-100: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T16:40:17Z" - latency: 2.262363ms message: 'network-check-target-ip-10-0-141-100: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T16:39:17Z" - latency: 2.24449ms message: 'network-check-target-ip-10-0-141-100: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T16:38:17Z" - latency: 2.397664ms message: 'network-check-target-ip-10-0-141-100: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T16:37:17Z" - latency: 2.277933ms message: 'network-check-target-ip-10-0-141-100: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T16:36:17Z" - latency: 2.310544ms message: 'network-check-target-ip-10-0-141-100: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T16:35:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T15:55:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-171-to-network-check-target-ip-10-0-141-146 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-171.ec2.internal uid: a15f2cbd-1808-4363-8bba-707552796bd5 resourceVersion: "71263" uid: 16cae126-59ec-4873-a1f8-7fc70ef71c80 spec: sourcePod: network-check-source-7d88cb55d8-2tgtj targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-27T16:02:17Z" message: 'network-check-target-ip-10-0-141-146: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.218446ms message: 'network-check-target-ip-10-0-141-146: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T16:44:17Z" - latency: 2.223369ms message: 'network-check-target-ip-10-0-141-146: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T16:43:17Z" - latency: 2.422767ms message: 'network-check-target-ip-10-0-141-146: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T16:42:17Z" - latency: 2.307776ms message: 'network-check-target-ip-10-0-141-146: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T16:41:17Z" - latency: 2.49148ms message: 'network-check-target-ip-10-0-141-146: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T16:40:17Z" - latency: 2.282104ms message: 'network-check-target-ip-10-0-141-146: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T16:39:17Z" - latency: 2.253684ms message: 'network-check-target-ip-10-0-141-146: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T16:38:17Z" - latency: 2.744797ms message: 'network-check-target-ip-10-0-141-146: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T16:37:17Z" - latency: 2.32ms message: 'network-check-target-ip-10-0-141-146: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T16:36:17Z" - latency: 2.436192ms message: 'network-check-target-ip-10-0-141-146: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T16:35:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T15:55:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-171-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-171.ec2.internal uid: a15f2cbd-1808-4363-8bba-707552796bd5 resourceVersion: "70437" uid: 6762bab7-09a0-4c59-afa9-d8fb1206b7a3 spec: sourcePod: network-check-source-7d88cb55d8-2tgtj targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-27T16:01:17Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.21556ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-27T16:43:17Z" - latency: 1.56653ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-27T16:43:17Z" - latency: 948.879µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-27T16:42:17Z" - latency: 1.922886ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-27T16:42:17Z" - latency: 1.164117ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-27T16:41:17Z" - latency: 1.711481ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-27T16:41:17Z" - latency: 1.416033ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-27T16:40:17Z" - latency: 2.055984ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-27T16:40:17Z" - latency: 897.954µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-27T16:39:17Z" - latency: 1.59616ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-27T16:39:17Z" kind: List metadata: resourceVersion: ""