apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T19:50:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-55-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-55.ec2.internal uid: 557f7787-2121-48d1-8629-4ef091099bb9 resourceVersion: "61476" uid: 274da7ee-970d-4548-ae2c-b04e03a6f431 spec: sourcePod: network-check-source-869dcfcdcd-5jsl2 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-14T19:57:23Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 976.328µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:32:23Z" - latency: 962.979µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:31:23Z" - latency: 1.214783ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:30:23Z" - latency: 1.12728ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:29:23Z" - latency: 1.202643ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:28:23Z" - latency: 1.148162ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:27:23Z" - latency: 1.112746ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:26:23Z" - latency: 966.083µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:25:23Z" - latency: 1.15879ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:24:23Z" - latency: 1.349679ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:23:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T19:50:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-55-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-55.ec2.internal uid: 557f7787-2121-48d1-8629-4ef091099bb9 resourceVersion: "61478" uid: cab0b01b-6441-4822-ab2a-760e7b4e731b spec: sourcePod: network-check-source-869dcfcdcd-5jsl2 targetEndpoint: ade400ce93b16497bbe7b710f3a4d7d1-0bd8620d70dd396a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-14T19:56:23Z" message: 'load-balancer-api-external: tcp connection to ade400ce93b16497bbe7b710f3a4d7d1-0bd8620d70dd396a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.526051ms message: 'load-balancer-api-external: tcp connection to ade400ce93b16497bbe7b710f3a4d7d1-0bd8620d70dd396a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:32:23Z" - latency: 8.333138ms message: 'load-balancer-api-external: resolved host name ade400ce93b16497bbe7b710f3a4d7d1-0bd8620d70dd396a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T20:32:23Z" - latency: 4.628787ms message: 'load-balancer-api-external: tcp connection to ade400ce93b16497bbe7b710f3a4d7d1-0bd8620d70dd396a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:31:23Z" - latency: 8.026539ms message: 'load-balancer-api-external: resolved host name ade400ce93b16497bbe7b710f3a4d7d1-0bd8620d70dd396a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T20:31:23Z" - latency: 4.207389ms message: 'load-balancer-api-external: tcp connection to ade400ce93b16497bbe7b710f3a4d7d1-0bd8620d70dd396a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:30:23Z" - latency: 8.561495ms message: 'load-balancer-api-external: resolved host name ade400ce93b16497bbe7b710f3a4d7d1-0bd8620d70dd396a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T20:30:23Z" - latency: 3.359055ms message: 'load-balancer-api-external: tcp connection to ade400ce93b16497bbe7b710f3a4d7d1-0bd8620d70dd396a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:29:23Z" - latency: 8.094701ms message: 'load-balancer-api-external: resolved host name ade400ce93b16497bbe7b710f3a4d7d1-0bd8620d70dd396a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T20:29:23Z" - latency: 5.052463ms message: 'load-balancer-api-external: tcp connection to ade400ce93b16497bbe7b710f3a4d7d1-0bd8620d70dd396a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:28:23Z" - latency: 8.263169ms message: 'load-balancer-api-external: resolved host name ade400ce93b16497bbe7b710f3a4d7d1-0bd8620d70dd396a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T20:28:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T19:50:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-55-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-55.ec2.internal uid: 557f7787-2121-48d1-8629-4ef091099bb9 resourceVersion: "61479" uid: d6621089-dde9-4eb3-8fa3-a05232d68578 spec: sourcePod: network-check-source-869dcfcdcd-5jsl2 targetEndpoint: ade400ce93b16497bbe7b710f3a4d7d1-0bd8620d70dd396a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-14T19:56:23Z" message: 'load-balancer-api-internal: tcp connection to ade400ce93b16497bbe7b710f3a4d7d1-0bd8620d70dd396a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.517749ms message: 'load-balancer-api-internal: tcp connection to ade400ce93b16497bbe7b710f3a4d7d1-0bd8620d70dd396a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:32:23Z" - latency: 8.410713ms message: 'load-balancer-api-internal: resolved host name ade400ce93b16497bbe7b710f3a4d7d1-0bd8620d70dd396a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T20:32:23Z" - latency: 4.711881ms message: 'load-balancer-api-internal: tcp connection to ade400ce93b16497bbe7b710f3a4d7d1-0bd8620d70dd396a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:31:23Z" - latency: 8.010682ms message: 'load-balancer-api-internal: resolved host name ade400ce93b16497bbe7b710f3a4d7d1-0bd8620d70dd396a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T20:31:23Z" - latency: 4.184789ms message: 'load-balancer-api-internal: tcp connection to ade400ce93b16497bbe7b710f3a4d7d1-0bd8620d70dd396a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:30:23Z" - latency: 8.517276ms message: 'load-balancer-api-internal: resolved host name ade400ce93b16497bbe7b710f3a4d7d1-0bd8620d70dd396a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T20:30:23Z" - latency: 2.891494ms message: 'load-balancer-api-internal: tcp connection to ade400ce93b16497bbe7b710f3a4d7d1-0bd8620d70dd396a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:29:23Z" - latency: 8.042643ms message: 'load-balancer-api-internal: resolved host name ade400ce93b16497bbe7b710f3a4d7d1-0bd8620d70dd396a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T20:29:23Z" - latency: 5.087014ms message: 'load-balancer-api-internal: tcp connection to ade400ce93b16497bbe7b710f3a4d7d1-0bd8620d70dd396a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:28:23Z" - latency: 8.183527ms message: 'load-balancer-api-internal: resolved host name ade400ce93b16497bbe7b710f3a4d7d1-0bd8620d70dd396a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T20:28:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T19:50:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-55-to-network-check-target-ip-10-0-129-28 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-55.ec2.internal uid: 557f7787-2121-48d1-8629-4ef091099bb9 resourceVersion: "61473" uid: 9a83a213-9f02-4ba1-8637-184a7ea414d0 spec: sourcePod: network-check-source-869dcfcdcd-5jsl2 targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-14T19:57:23Z" message: 'network-check-target-ip-10-0-129-28: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.980011ms message: 'network-check-target-ip-10-0-129-28: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:32:23Z" - latency: 2.252463ms message: 'network-check-target-ip-10-0-129-28: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:31:23Z" - latency: 2.106472ms message: 'network-check-target-ip-10-0-129-28: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:30:23Z" - latency: 2.093841ms message: 'network-check-target-ip-10-0-129-28: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:29:23Z" - latency: 2.219595ms message: 'network-check-target-ip-10-0-129-28: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:28:23Z" - latency: 2.115286ms message: 'network-check-target-ip-10-0-129-28: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:27:23Z" - latency: 2.346742ms message: 'network-check-target-ip-10-0-129-28: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:26:23Z" - latency: 2.223135ms message: 'network-check-target-ip-10-0-129-28: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:25:23Z" - latency: 2.052999ms message: 'network-check-target-ip-10-0-129-28: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:24:23Z" - latency: 2.385069ms message: 'network-check-target-ip-10-0-129-28: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:23:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T19:50:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-55-to-network-check-target-ip-10-0-130-55 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-55.ec2.internal uid: 557f7787-2121-48d1-8629-4ef091099bb9 resourceVersion: "61472" uid: 3320e736-752d-4b95-b33f-745446dcf191 spec: sourcePod: network-check-source-869dcfcdcd-5jsl2 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-14T19:57:23Z" message: 'network-check-target-ip-10-0-130-55: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.095251ms message: 'network-check-target-ip-10-0-130-55: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:32:23Z" - latency: 1.152624ms message: 'network-check-target-ip-10-0-130-55: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:31:23Z" - latency: 951.165µs message: 'network-check-target-ip-10-0-130-55: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:30:23Z" - latency: 862.329µs message: 'network-check-target-ip-10-0-130-55: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:29:23Z" - latency: 907.88µs message: 'network-check-target-ip-10-0-130-55: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:28:23Z" - latency: 890.849µs message: 'network-check-target-ip-10-0-130-55: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:27:23Z" - latency: 895.114µs message: 'network-check-target-ip-10-0-130-55: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:26:23Z" - latency: 763.986µs message: 'network-check-target-ip-10-0-130-55: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:25:23Z" - latency: 859.639µs message: 'network-check-target-ip-10-0-130-55: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:24:23Z" - latency: 1.230682ms message: 'network-check-target-ip-10-0-130-55: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:23:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T19:50:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-55-to-network-check-target-ip-10-0-133-168 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-55.ec2.internal uid: 557f7787-2121-48d1-8629-4ef091099bb9 resourceVersion: "61474" uid: f568422a-1b8b-4e53-90fa-96baa99728d2 spec: sourcePod: network-check-source-869dcfcdcd-5jsl2 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-14T19:57:23Z" message: 'network-check-target-ip-10-0-133-168: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.510237ms message: 'network-check-target-ip-10-0-133-168: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:32:23Z" - latency: 2.301482ms message: 'network-check-target-ip-10-0-133-168: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:31:23Z" - latency: 2.538197ms message: 'network-check-target-ip-10-0-133-168: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:30:23Z" - latency: 2.188455ms message: 'network-check-target-ip-10-0-133-168: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:29:23Z" - latency: 2.192062ms message: 'network-check-target-ip-10-0-133-168: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:28:23Z" - latency: 2.449902ms message: 'network-check-target-ip-10-0-133-168: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:27:23Z" - latency: 2.230626ms message: 'network-check-target-ip-10-0-133-168: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:26:23Z" - latency: 2.492491ms message: 'network-check-target-ip-10-0-133-168: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:25:23Z" - latency: 2.344119ms message: 'network-check-target-ip-10-0-133-168: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:24:23Z" - latency: 2.081911ms message: 'network-check-target-ip-10-0-133-168: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:23:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T19:50:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-55-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-55.ec2.internal uid: 557f7787-2121-48d1-8629-4ef091099bb9 resourceVersion: "61475" uid: c0ae02ab-6d98-4b55-b686-876d1d0dfbc7 spec: sourcePod: network-check-source-869dcfcdcd-5jsl2 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-14T19:56:23Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.157887ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:32:23Z" - latency: 1.700651ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-14T20:32:23Z" - latency: 999.711µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:31:23Z" - latency: 1.908585ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-14T20:31:23Z" - latency: 1.360402ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:30:23Z" - latency: 1.863017ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-14T20:30:23Z" - latency: 1.232059ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:29:23Z" - latency: 1.798372ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-14T20:29:23Z" - latency: 768.51µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:28:23Z" - latency: 1.67751ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-14T20:28:23Z" kind: List metadata: resourceVersion: ""