apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T14:03:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-3-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-3.ec2.internal uid: 6c5a7b14-507d-4e23-b35a-656e37d4826b resourceVersion: "33307" uid: f4111b57-050e-450f-b2c0-28e03fe4ed3d spec: sourcePod: network-check-source-7b678d77c7-cwrlm targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-16T14:10:52Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.071327ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:24:52Z" - latency: 1.176723ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:23:52Z" - latency: 1.066268ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:22:52Z" - latency: 1.02944ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:21:52Z" - latency: 1.10017ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:20:52Z" - latency: 898.171µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:19:52Z" - latency: 901.34µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:18:52Z" - latency: 780.053µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:17:52Z" - latency: 915.409µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:16:52Z" - latency: 953.611µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:15:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T14:03:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-3-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-3.ec2.internal uid: 6c5a7b14-507d-4e23-b35a-656e37d4826b resourceVersion: "35846" uid: 7c18201b-74dc-4f0a-99bd-5cdb18b121e0 spec: sourcePod: network-check-source-7b678d77c7-cwrlm targetEndpoint: a1753f2b8501641079f33df55b4595f2-4705fbe3595c6e91.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-16T14:09:52Z" message: 'load-balancer-api-external: tcp connection to a1753f2b8501641079f33df55b4595f2-4705fbe3595c6e91.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.8759ms message: 'load-balancer-api-external: tcp connection to a1753f2b8501641079f33df55b4595f2-4705fbe3595c6e91.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:27:52Z" - latency: 5.430355ms message: 'load-balancer-api-external: resolved host name a1753f2b8501641079f33df55b4595f2-4705fbe3595c6e91.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T14:27:52Z" - latency: 5.891157ms message: 'load-balancer-api-external: tcp connection to a1753f2b8501641079f33df55b4595f2-4705fbe3595c6e91.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:26:52Z" - latency: 7.325948ms message: 'load-balancer-api-external: resolved host name a1753f2b8501641079f33df55b4595f2-4705fbe3595c6e91.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T14:26:52Z" - latency: 4.691937ms message: 'load-balancer-api-external: tcp connection to a1753f2b8501641079f33df55b4595f2-4705fbe3595c6e91.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:25:52Z" - latency: 5.95594ms message: 'load-balancer-api-external: resolved host name a1753f2b8501641079f33df55b4595f2-4705fbe3595c6e91.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T14:25:52Z" - latency: 4.988951ms message: 'load-balancer-api-external: tcp connection to a1753f2b8501641079f33df55b4595f2-4705fbe3595c6e91.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:24:52Z" - latency: 6.772356ms message: 'load-balancer-api-external: resolved host name a1753f2b8501641079f33df55b4595f2-4705fbe3595c6e91.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T14:24:52Z" - latency: 5.665196ms message: 'load-balancer-api-external: tcp connection to a1753f2b8501641079f33df55b4595f2-4705fbe3595c6e91.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:23:52Z" - latency: 6.267027ms message: 'load-balancer-api-external: resolved host name a1753f2b8501641079f33df55b4595f2-4705fbe3595c6e91.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T14:23:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T14:03:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-3-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-3.ec2.internal uid: 6c5a7b14-507d-4e23-b35a-656e37d4826b resourceVersion: "35845" uid: c08c294f-158b-4a89-819d-009a378ff183 spec: sourcePod: network-check-source-7b678d77c7-cwrlm targetEndpoint: a1753f2b8501641079f33df55b4595f2-4705fbe3595c6e91.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-16T14:09:52Z" message: 'load-balancer-api-internal: tcp connection to a1753f2b8501641079f33df55b4595f2-4705fbe3595c6e91.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.92881ms message: 'load-balancer-api-internal: tcp connection to a1753f2b8501641079f33df55b4595f2-4705fbe3595c6e91.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:27:52Z" - latency: 6.622108ms message: 'load-balancer-api-internal: resolved host name a1753f2b8501641079f33df55b4595f2-4705fbe3595c6e91.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T14:27:52Z" - latency: 4.636929ms message: 'load-balancer-api-internal: tcp connection to a1753f2b8501641079f33df55b4595f2-4705fbe3595c6e91.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:26:52Z" - latency: 7.297899ms message: 'load-balancer-api-internal: resolved host name a1753f2b8501641079f33df55b4595f2-4705fbe3595c6e91.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T14:26:52Z" - latency: 5.432181ms message: 'load-balancer-api-internal: tcp connection to a1753f2b8501641079f33df55b4595f2-4705fbe3595c6e91.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:25:52Z" - latency: 5.849448ms message: 'load-balancer-api-internal: resolved host name a1753f2b8501641079f33df55b4595f2-4705fbe3595c6e91.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T14:25:52Z" - latency: 5.249233ms message: 'load-balancer-api-internal: tcp connection to a1753f2b8501641079f33df55b4595f2-4705fbe3595c6e91.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:24:52Z" - latency: 6.737116ms message: 'load-balancer-api-internal: resolved host name a1753f2b8501641079f33df55b4595f2-4705fbe3595c6e91.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T14:24:52Z" - latency: 5.613099ms message: 'load-balancer-api-internal: tcp connection to a1753f2b8501641079f33df55b4595f2-4705fbe3595c6e91.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:23:52Z" - latency: 6.30246ms message: 'load-balancer-api-internal: resolved host name a1753f2b8501641079f33df55b4595f2-4705fbe3595c6e91.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T14:23:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T14:03:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-3-to-network-check-target-ip-10-0-129-3 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-3.ec2.internal uid: 6c5a7b14-507d-4e23-b35a-656e37d4826b resourceVersion: "33304" uid: 0ae46c71-bd73-4e07-b2e5-6b2540091b6c spec: sourcePod: network-check-source-7b678d77c7-cwrlm targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-16T14:10:52Z" message: 'network-check-target-ip-10-0-129-3: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 884.843µs message: 'network-check-target-ip-10-0-129-3: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:24:52Z" - latency: 1.223802ms message: 'network-check-target-ip-10-0-129-3: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:23:52Z" - latency: 1.096249ms message: 'network-check-target-ip-10-0-129-3: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:22:52Z" - latency: 1.235927ms message: 'network-check-target-ip-10-0-129-3: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:21:52Z" - latency: 1.635044ms message: 'network-check-target-ip-10-0-129-3: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:20:52Z" - latency: 849.433µs message: 'network-check-target-ip-10-0-129-3: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:19:52Z" - latency: 1.223422ms message: 'network-check-target-ip-10-0-129-3: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:18:52Z" - latency: 915.794µs message: 'network-check-target-ip-10-0-129-3: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:17:52Z" - latency: 853.752µs message: 'network-check-target-ip-10-0-129-3: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:16:52Z" - latency: 970.495µs message: 'network-check-target-ip-10-0-129-3: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:15:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T14:03:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-3-to-network-check-target-ip-10-0-131-99 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-3.ec2.internal uid: 6c5a7b14-507d-4e23-b35a-656e37d4826b resourceVersion: "33306" uid: b7a8cb11-528e-4977-b37e-9ba45f977676 spec: sourcePod: network-check-source-7b678d77c7-cwrlm targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-16T14:10:52Z" message: 'network-check-target-ip-10-0-131-99: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.332843ms message: 'network-check-target-ip-10-0-131-99: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:24:52Z" - latency: 2.767124ms message: 'network-check-target-ip-10-0-131-99: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:23:52Z" - latency: 2.27558ms message: 'network-check-target-ip-10-0-131-99: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:22:52Z" - latency: 2.201588ms message: 'network-check-target-ip-10-0-131-99: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:21:52Z" - latency: 2.451482ms message: 'network-check-target-ip-10-0-131-99: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:20:52Z" - latency: 2.11476ms message: 'network-check-target-ip-10-0-131-99: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:19:52Z" - latency: 2.404483ms message: 'network-check-target-ip-10-0-131-99: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:18:52Z" - latency: 2.444767ms message: 'network-check-target-ip-10-0-131-99: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:17:52Z" - latency: 2.285663ms message: 'network-check-target-ip-10-0-131-99: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:16:52Z" - latency: 2.074804ms message: 'network-check-target-ip-10-0-131-99: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:15:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T14:03:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-3-to-network-check-target-ip-10-0-140-244 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-3.ec2.internal uid: 6c5a7b14-507d-4e23-b35a-656e37d4826b resourceVersion: "33305" uid: dff7dad9-9a8d-429d-98fa-089da7dd7b60 spec: sourcePod: network-check-source-7b678d77c7-cwrlm targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-16T14:10:52Z" message: 'network-check-target-ip-10-0-140-244: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.815553ms message: 'network-check-target-ip-10-0-140-244: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:24:52Z" - latency: 1.898738ms message: 'network-check-target-ip-10-0-140-244: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:23:52Z" - latency: 2.038608ms message: 'network-check-target-ip-10-0-140-244: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:22:52Z" - latency: 1.868503ms message: 'network-check-target-ip-10-0-140-244: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:21:52Z" - latency: 1.963333ms message: 'network-check-target-ip-10-0-140-244: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:20:52Z" - latency: 2.092729ms message: 'network-check-target-ip-10-0-140-244: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:19:52Z" - latency: 1.920336ms message: 'network-check-target-ip-10-0-140-244: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:18:52Z" - latency: 2.214333ms message: 'network-check-target-ip-10-0-140-244: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:17:52Z" - latency: 1.90358ms message: 'network-check-target-ip-10-0-140-244: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:16:52Z" - latency: 1.788789ms message: 'network-check-target-ip-10-0-140-244: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:15:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T14:03:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-3-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-3.ec2.internal uid: 6c5a7b14-507d-4e23-b35a-656e37d4826b resourceVersion: "35844" uid: ea191b9c-33f7-46d9-9016-d150e0ef0f33 spec: sourcePod: network-check-source-7b678d77c7-cwrlm targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-16T14:09:52Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.042362ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:27:52Z" - latency: 1.956371ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T14:27:52Z" - latency: 983.497µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:26:52Z" - latency: 1.911603ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T14:26:52Z" - latency: 835.31µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:25:52Z" - latency: 1.490222ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T14:25:52Z" - latency: 1.525616ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:24:52Z" - latency: 1.970922ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T14:24:52Z" - latency: 710.552µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:23:52Z" - latency: 1.596826ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T14:23:52Z" kind: List metadata: resourceVersion: ""