apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T20:55:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-13-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-13.ec2.internal uid: 185572ec-cd0b-41b1-a65a-9e285bf9f0e5 resourceVersion: "53917" uid: 31187847-a1a4-4592-86d7-3b5897edad85 spec: sourcePod: network-check-source-685456655f-grx2v targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-09-09T21:02:32Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.159167ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:23:32Z" - latency: 911.402µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:22:32Z" - latency: 1.059784ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:21:32Z" - latency: 1.264055ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:20:32Z" - latency: 1.122539ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:19:32Z" - latency: 1.229945ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:18:32Z" - latency: 1.232899ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:17:32Z" - latency: 1.275933ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:16:32Z" - latency: 941.598µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:15:32Z" - latency: 1.189954ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:14:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T20:55:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-13-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-13.ec2.internal uid: 185572ec-cd0b-41b1-a65a-9e285bf9f0e5 resourceVersion: "55653" uid: 799a8bc1-cb2f-429e-b33e-856ce63ebcf2 spec: sourcePod: network-check-source-685456655f-grx2v targetEndpoint: ac092e7aac7aa4b64a003d449c137ad2-4d400d18f2e19090.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-09T21:01:32Z" message: 'load-balancer-api-external: tcp connection to ac092e7aac7aa4b64a003d449c137ad2-4d400d18f2e19090.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.487181ms message: 'load-balancer-api-external: tcp connection to ac092e7aac7aa4b64a003d449c137ad2-4d400d18f2e19090.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:25:32Z" - latency: 9.035934ms message: 'load-balancer-api-external: resolved host name ac092e7aac7aa4b64a003d449c137ad2-4d400d18f2e19090.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T21:25:32Z" - latency: 4.95693ms message: 'load-balancer-api-external: tcp connection to ac092e7aac7aa4b64a003d449c137ad2-4d400d18f2e19090.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:24:32Z" - latency: 8.686436ms message: 'load-balancer-api-external: resolved host name ac092e7aac7aa4b64a003d449c137ad2-4d400d18f2e19090.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T21:24:32Z" - latency: 3.190463ms message: 'load-balancer-api-external: tcp connection to ac092e7aac7aa4b64a003d449c137ad2-4d400d18f2e19090.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:23:32Z" - latency: 8.338455ms message: 'load-balancer-api-external: resolved host name ac092e7aac7aa4b64a003d449c137ad2-4d400d18f2e19090.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T21:23:32Z" - latency: 4.884413ms message: 'load-balancer-api-external: tcp connection to ac092e7aac7aa4b64a003d449c137ad2-4d400d18f2e19090.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:22:32Z" - latency: 10.41138ms message: 'load-balancer-api-external: resolved host name ac092e7aac7aa4b64a003d449c137ad2-4d400d18f2e19090.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T21:22:32Z" - latency: 4.566654ms message: 'load-balancer-api-external: tcp connection to ac092e7aac7aa4b64a003d449c137ad2-4d400d18f2e19090.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:21:32Z" - latency: 8.866465ms message: 'load-balancer-api-external: resolved host name ac092e7aac7aa4b64a003d449c137ad2-4d400d18f2e19090.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T21:21:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T20:55:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-13-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-13.ec2.internal uid: 185572ec-cd0b-41b1-a65a-9e285bf9f0e5 resourceVersion: "55654" uid: 2f509961-191d-4bbb-b25e-4ccbb574b282 spec: sourcePod: network-check-source-685456655f-grx2v targetEndpoint: ac092e7aac7aa4b64a003d449c137ad2-4d400d18f2e19090.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-09T21:01:32Z" message: 'load-balancer-api-internal: tcp connection to ac092e7aac7aa4b64a003d449c137ad2-4d400d18f2e19090.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.517985ms message: 'load-balancer-api-internal: tcp connection to ac092e7aac7aa4b64a003d449c137ad2-4d400d18f2e19090.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:25:32Z" - latency: 8.997919ms message: 'load-balancer-api-internal: resolved host name ac092e7aac7aa4b64a003d449c137ad2-4d400d18f2e19090.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T21:25:32Z" - latency: 4.929081ms message: 'load-balancer-api-internal: tcp connection to ac092e7aac7aa4b64a003d449c137ad2-4d400d18f2e19090.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:24:32Z" - latency: 8.713521ms message: 'load-balancer-api-internal: resolved host name ac092e7aac7aa4b64a003d449c137ad2-4d400d18f2e19090.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T21:24:32Z" - latency: 4.006053ms message: 'load-balancer-api-internal: tcp connection to ac092e7aac7aa4b64a003d449c137ad2-4d400d18f2e19090.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:23:32Z" - latency: 8.370612ms message: 'load-balancer-api-internal: resolved host name ac092e7aac7aa4b64a003d449c137ad2-4d400d18f2e19090.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T21:23:32Z" - latency: 5.927398ms message: 'load-balancer-api-internal: tcp connection to ac092e7aac7aa4b64a003d449c137ad2-4d400d18f2e19090.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:22:32Z" - latency: 10.443839ms message: 'load-balancer-api-internal: resolved host name ac092e7aac7aa4b64a003d449c137ad2-4d400d18f2e19090.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T21:22:32Z" - latency: 4.605916ms message: 'load-balancer-api-internal: tcp connection to ac092e7aac7aa4b64a003d449c137ad2-4d400d18f2e19090.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:21:32Z" - latency: 8.777234ms message: 'load-balancer-api-internal: resolved host name ac092e7aac7aa4b64a003d449c137ad2-4d400d18f2e19090.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T21:21:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T20:55:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-13-to-network-check-target-ip-10-0-129-13 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-13.ec2.internal uid: 185572ec-cd0b-41b1-a65a-9e285bf9f0e5 resourceVersion: "53914" uid: 0398599f-389a-4438-9a6c-32b39bb4731a spec: sourcePod: network-check-source-685456655f-grx2v targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-09-09T21:02:32Z" message: 'network-check-target-ip-10-0-129-13: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.030127ms message: 'network-check-target-ip-10-0-129-13: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:23:32Z" - latency: 1.231161ms message: 'network-check-target-ip-10-0-129-13: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:22:32Z" - latency: 1.20216ms message: 'network-check-target-ip-10-0-129-13: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:21:32Z" - latency: 1.068969ms message: 'network-check-target-ip-10-0-129-13: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:20:32Z" - latency: 925.477µs message: 'network-check-target-ip-10-0-129-13: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:19:32Z" - latency: 1.08705ms message: 'network-check-target-ip-10-0-129-13: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:18:32Z" - latency: 1.442206ms message: 'network-check-target-ip-10-0-129-13: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:17:32Z" - latency: 826.435µs message: 'network-check-target-ip-10-0-129-13: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:16:32Z" - latency: 1.007911ms message: 'network-check-target-ip-10-0-129-13: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:15:32Z" - latency: 956.518µs message: 'network-check-target-ip-10-0-129-13: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:14:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T20:55:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-13-to-network-check-target-ip-10-0-134-62 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-13.ec2.internal uid: 185572ec-cd0b-41b1-a65a-9e285bf9f0e5 resourceVersion: "53916" uid: 0cddee66-0046-4bf0-9663-a41e517c3cfe spec: sourcePod: network-check-source-685456655f-grx2v targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-09-09T21:02:32Z" message: 'network-check-target-ip-10-0-134-62: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.56068ms message: 'network-check-target-ip-10-0-134-62: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:23:32Z" - latency: 1.834716ms message: 'network-check-target-ip-10-0-134-62: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:22:32Z" - latency: 2.346305ms message: 'network-check-target-ip-10-0-134-62: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:21:32Z" - latency: 2.548727ms message: 'network-check-target-ip-10-0-134-62: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:20:32Z" - latency: 2.492459ms message: 'network-check-target-ip-10-0-134-62: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:19:32Z" - latency: 3.053264ms message: 'network-check-target-ip-10-0-134-62: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:18:32Z" - latency: 2.762375ms message: 'network-check-target-ip-10-0-134-62: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:17:32Z" - latency: 2.225443ms message: 'network-check-target-ip-10-0-134-62: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:16:32Z" - latency: 2.918136ms message: 'network-check-target-ip-10-0-134-62: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:15:32Z" - latency: 2.536073ms message: 'network-check-target-ip-10-0-134-62: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:14:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T20:55:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-13-to-network-check-target-ip-10-0-136-121 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-13.ec2.internal uid: 185572ec-cd0b-41b1-a65a-9e285bf9f0e5 resourceVersion: "53915" uid: 11707a89-4ef3-40a8-8972-715973814e7f spec: sourcePod: network-check-source-685456655f-grx2v targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-09-09T21:02:32Z" message: 'network-check-target-ip-10-0-136-121: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.902304ms message: 'network-check-target-ip-10-0-136-121: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:23:32Z" - latency: 1.903883ms message: 'network-check-target-ip-10-0-136-121: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:22:32Z" - latency: 2.483755ms message: 'network-check-target-ip-10-0-136-121: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:21:32Z" - latency: 2.46399ms message: 'network-check-target-ip-10-0-136-121: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:20:32Z" - latency: 2.428924ms message: 'network-check-target-ip-10-0-136-121: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:19:32Z" - latency: 2.391514ms message: 'network-check-target-ip-10-0-136-121: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:18:32Z" - latency: 2.255709ms message: 'network-check-target-ip-10-0-136-121: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:17:32Z" - latency: 2.003787ms message: 'network-check-target-ip-10-0-136-121: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:16:32Z" - latency: 2.566914ms message: 'network-check-target-ip-10-0-136-121: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:15:32Z" - latency: 2.608634ms message: 'network-check-target-ip-10-0-136-121: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:14:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T20:55:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-13-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-13.ec2.internal uid: 185572ec-cd0b-41b1-a65a-9e285bf9f0e5 resourceVersion: "55652" uid: e0915d85-0305-4e11-bacd-859ae58dac39 spec: sourcePod: network-check-source-685456655f-grx2v targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-09-09T21:01:32Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 950.517µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:25:32Z" - latency: 1.858944ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-09T21:25:32Z" - latency: 912.708µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:24:32Z" - latency: 2.161432ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-09T21:24:32Z" - latency: 863.401µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:23:32Z" - latency: 1.871736ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-09T21:23:32Z" - latency: 935.257µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:22:32Z" - latency: 1.848322ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-09T21:22:32Z" - latency: 873.547µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:21:32Z" - latency: 1.845677ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-09T21:21:32Z" kind: List metadata: resourceVersion: ""