apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T18:43:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-211-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-211.ec2.internal uid: c36633fb-d30c-4922-a63b-0b875db25df1 resourceVersion: "30442" uid: a0eb46f3-37a6-4fb2-a6e2-6c177b819892 spec: sourcePod: network-check-source-56d84b9f44-t65zt targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-02T18:50:55Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.111115ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T18:57:55Z" - latency: 976.551µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T18:56:55Z" - latency: 1.15331ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T18:55:55Z" - latency: 1.083635ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T18:54:55Z" - latency: 1.117909ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T18:53:55Z" - latency: 1.788424ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T18:52:55Z" - latency: 1.164565ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T18:51:55Z" - latency: 821.549µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T18:50:55Z" - latency: 864.632µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T18:49:55Z" - latency: 1.729796ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T18:48:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T18:43:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-211-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-211.ec2.internal uid: c36633fb-d30c-4922-a63b-0b875db25df1 resourceVersion: "28901" uid: 310f5684-0147-4ee6-9b6f-2d7333b02889 spec: sourcePod: network-check-source-56d84b9f44-t65zt targetEndpoint: a4c3b6505c4364369882accb5e3988ee-c0d1d57514cb2a29.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-02T18:49:55Z" message: 'load-balancer-api-external: tcp connection to a4c3b6505c4364369882accb5e3988ee-c0d1d57514cb2a29.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.528461ms message: 'load-balancer-api-external: tcp connection to a4c3b6505c4364369882accb5e3988ee-c0d1d57514cb2a29.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T18:55:55Z" - latency: 6.710634ms message: 'load-balancer-api-external: resolved host name a4c3b6505c4364369882accb5e3988ee-c0d1d57514cb2a29.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T18:55:55Z" - latency: 4.762852ms message: 'load-balancer-api-external: tcp connection to a4c3b6505c4364369882accb5e3988ee-c0d1d57514cb2a29.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T18:54:55Z" - latency: 6.813288ms message: 'load-balancer-api-external: resolved host name a4c3b6505c4364369882accb5e3988ee-c0d1d57514cb2a29.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T18:54:55Z" - latency: 5.200737ms message: 'load-balancer-api-external: tcp connection to a4c3b6505c4364369882accb5e3988ee-c0d1d57514cb2a29.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T18:53:55Z" - latency: 7.485154ms message: 'load-balancer-api-external: resolved host name a4c3b6505c4364369882accb5e3988ee-c0d1d57514cb2a29.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T18:53:55Z" - latency: 5.288231ms message: 'load-balancer-api-external: tcp connection to a4c3b6505c4364369882accb5e3988ee-c0d1d57514cb2a29.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T18:52:55Z" - latency: 7.314564ms message: 'load-balancer-api-external: resolved host name a4c3b6505c4364369882accb5e3988ee-c0d1d57514cb2a29.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T18:52:55Z" - latency: 5.328239ms message: 'load-balancer-api-external: tcp connection to a4c3b6505c4364369882accb5e3988ee-c0d1d57514cb2a29.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T18:51:55Z" - latency: 6.775245ms message: 'load-balancer-api-external: resolved host name a4c3b6505c4364369882accb5e3988ee-c0d1d57514cb2a29.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T18:51:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T18:43:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-211-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-211.ec2.internal uid: c36633fb-d30c-4922-a63b-0b875db25df1 resourceVersion: "28902" uid: 7c1b409a-1a81-4a05-ba14-28a129b8965d spec: sourcePod: network-check-source-56d84b9f44-t65zt targetEndpoint: a4c3b6505c4364369882accb5e3988ee-c0d1d57514cb2a29.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-02T18:49:55Z" message: 'load-balancer-api-internal: tcp connection to a4c3b6505c4364369882accb5e3988ee-c0d1d57514cb2a29.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.554112ms message: 'load-balancer-api-internal: tcp connection to a4c3b6505c4364369882accb5e3988ee-c0d1d57514cb2a29.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T18:55:55Z" - latency: 6.584182ms message: 'load-balancer-api-internal: resolved host name a4c3b6505c4364369882accb5e3988ee-c0d1d57514cb2a29.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T18:55:55Z" - latency: 4.7666ms message: 'load-balancer-api-internal: tcp connection to a4c3b6505c4364369882accb5e3988ee-c0d1d57514cb2a29.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T18:54:55Z" - latency: 6.856727ms message: 'load-balancer-api-internal: resolved host name a4c3b6505c4364369882accb5e3988ee-c0d1d57514cb2a29.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T18:54:55Z" - latency: 5.311215ms message: 'load-balancer-api-internal: tcp connection to a4c3b6505c4364369882accb5e3988ee-c0d1d57514cb2a29.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T18:53:55Z" - latency: 7.415936ms message: 'load-balancer-api-internal: resolved host name a4c3b6505c4364369882accb5e3988ee-c0d1d57514cb2a29.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T18:53:55Z" - latency: 5.213806ms message: 'load-balancer-api-internal: tcp connection to a4c3b6505c4364369882accb5e3988ee-c0d1d57514cb2a29.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T18:52:55Z" - latency: 7.3618ms message: 'load-balancer-api-internal: resolved host name a4c3b6505c4364369882accb5e3988ee-c0d1d57514cb2a29.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T18:52:55Z" - latency: 4.357624ms message: 'load-balancer-api-internal: tcp connection to a4c3b6505c4364369882accb5e3988ee-c0d1d57514cb2a29.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T18:51:55Z" - latency: 6.745357ms message: 'load-balancer-api-internal: resolved host name a4c3b6505c4364369882accb5e3988ee-c0d1d57514cb2a29.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T18:51:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T18:43:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-211-to-network-check-target-ip-10-0-128-123 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-211.ec2.internal uid: c36633fb-d30c-4922-a63b-0b875db25df1 resourceVersion: "30440" uid: 1ab484b1-b819-4f67-86b5-f3abcfb5725d spec: sourcePod: network-check-source-56d84b9f44-t65zt targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-02T18:50:55Z" message: 'network-check-target-ip-10-0-128-123: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.157815ms message: 'network-check-target-ip-10-0-128-123: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T18:57:55Z" - latency: 2.357214ms message: 'network-check-target-ip-10-0-128-123: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T18:56:55Z" - latency: 2.225826ms message: 'network-check-target-ip-10-0-128-123: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T18:55:55Z" - latency: 2.16789ms message: 'network-check-target-ip-10-0-128-123: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T18:54:55Z" - latency: 2.080618ms message: 'network-check-target-ip-10-0-128-123: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T18:53:55Z" - latency: 2.729371ms message: 'network-check-target-ip-10-0-128-123: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T18:52:55Z" - latency: 2.214301ms message: 'network-check-target-ip-10-0-128-123: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T18:51:55Z" - latency: 2.114435ms message: 'network-check-target-ip-10-0-128-123: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T18:50:55Z" - latency: 2.345588ms message: 'network-check-target-ip-10-0-128-123: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T18:49:55Z" - latency: 2.807365ms message: 'network-check-target-ip-10-0-128-123: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T18:48:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T18:43:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-211-to-network-check-target-ip-10-0-130-211 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-211.ec2.internal uid: c36633fb-d30c-4922-a63b-0b875db25df1 resourceVersion: "30439" uid: 3a23039b-4faa-43b0-be12-804306637d4c spec: sourcePod: network-check-source-56d84b9f44-t65zt targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-02T18:50:55Z" message: 'network-check-target-ip-10-0-130-211: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.005765ms message: 'network-check-target-ip-10-0-130-211: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T18:57:55Z" - latency: 1.329981ms message: 'network-check-target-ip-10-0-130-211: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T18:56:55Z" - latency: 817.974µs message: 'network-check-target-ip-10-0-130-211: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T18:55:55Z" - latency: 1.337215ms message: 'network-check-target-ip-10-0-130-211: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T18:54:55Z" - latency: 901.931µs message: 'network-check-target-ip-10-0-130-211: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T18:53:55Z" - latency: 1.446796ms message: 'network-check-target-ip-10-0-130-211: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T18:52:55Z" - latency: 1.492438ms message: 'network-check-target-ip-10-0-130-211: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T18:51:55Z" - latency: 1.530234ms message: 'network-check-target-ip-10-0-130-211: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T18:50:55Z" - latency: 1.102159ms message: 'network-check-target-ip-10-0-130-211: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T18:49:55Z" - latency: 1.087796ms message: 'network-check-target-ip-10-0-130-211: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T18:48:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T18:43:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-211-to-network-check-target-ip-10-0-140-185 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-211.ec2.internal uid: c36633fb-d30c-4922-a63b-0b875db25df1 resourceVersion: "30441" uid: 906bf8c7-7d05-4bc1-b4b5-92d7e052edcc spec: sourcePod: network-check-source-56d84b9f44-t65zt targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-02T18:50:55Z" message: 'network-check-target-ip-10-0-140-185: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.779651ms message: 'network-check-target-ip-10-0-140-185: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T18:57:55Z" - latency: 1.918705ms message: 'network-check-target-ip-10-0-140-185: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T18:56:55Z" - latency: 1.918268ms message: 'network-check-target-ip-10-0-140-185: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T18:55:55Z" - latency: 1.504682ms message: 'network-check-target-ip-10-0-140-185: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T18:54:55Z" - latency: 1.993086ms message: 'network-check-target-ip-10-0-140-185: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T18:53:55Z" - latency: 1.989654ms message: 'network-check-target-ip-10-0-140-185: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T18:52:55Z" - latency: 1.979428ms message: 'network-check-target-ip-10-0-140-185: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T18:51:55Z" - latency: 2.039029ms message: 'network-check-target-ip-10-0-140-185: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T18:50:55Z" - latency: 2.199327ms message: 'network-check-target-ip-10-0-140-185: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T18:49:55Z" - latency: 2.684253ms message: 'network-check-target-ip-10-0-140-185: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T18:48:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T18:43:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-211-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-211.ec2.internal uid: c36633fb-d30c-4922-a63b-0b875db25df1 resourceVersion: "28900" uid: 2cfdbd53-5030-4b27-8f22-203c83e01102 spec: sourcePod: network-check-source-56d84b9f44-t65zt targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-02T18:49:55Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 862.74µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-02T18:55:55Z" - latency: 1.90971ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-02T18:55:55Z" - latency: 913.71µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-02T18:54:55Z" - latency: 1.559417ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-02T18:54:55Z" - latency: 908.533µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-02T18:53:55Z" - latency: 2.162013ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-02T18:53:55Z" - latency: 884.207µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-02T18:52:55Z" - latency: 2.394992ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-02T18:52:55Z" - latency: 918.93µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-02T18:51:55Z" - latency: 2.170219ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-02T18:51:55Z" kind: List metadata: resourceVersion: ""