apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T00:05:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-78-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-78.ec2.internal uid: 947db32b-493e-4a65-8fcc-66b3e6f82525 resourceVersion: "25364" uid: c8efa62e-dfb8-4af5-ba1a-61e11a90c288 spec: sourcePod: network-check-source-dbd9cf844-j2ptb targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-09T00:12:14Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.0134ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T00:12:14Z" - latency: 1.272037ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T00:11:14Z" - latency: 1.220588ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T00:10:14Z" - latency: 1.073948ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T00:09:14Z" - latency: 1.082732ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T00:08:14Z" - latency: 866.511µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T00:07:14Z" - latency: 1.050352ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T00:06:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T00:05:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-78-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-78.ec2.internal uid: 947db32b-493e-4a65-8fcc-66b3e6f82525 resourceVersion: "30699" uid: 5f4f2e05-4dbc-4998-af2a-7dd924d4d9fe spec: sourcePod: network-check-source-dbd9cf844-j2ptb targetEndpoint: ac958be462187409e9edf3b2fe038d0e-65d752e864c50dff.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-09T00:11:14Z" message: 'load-balancer-api-external: tcp connection to ac958be462187409e9edf3b2fe038d0e-65d752e864c50dff.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.814116ms message: 'load-balancer-api-external: tcp connection to ac958be462187409e9edf3b2fe038d0e-65d752e864c50dff.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T00:17:14Z" - latency: 6.488224ms message: 'load-balancer-api-external: resolved host name ac958be462187409e9edf3b2fe038d0e-65d752e864c50dff.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T00:17:14Z" - latency: 5.167851ms message: 'load-balancer-api-external: tcp connection to ac958be462187409e9edf3b2fe038d0e-65d752e864c50dff.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T00:16:14Z" - latency: 7.035273ms message: 'load-balancer-api-external: resolved host name ac958be462187409e9edf3b2fe038d0e-65d752e864c50dff.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T00:16:14Z" - latency: 3.945272ms message: 'load-balancer-api-external: tcp connection to ac958be462187409e9edf3b2fe038d0e-65d752e864c50dff.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T00:15:14Z" - latency: 6.882164ms message: 'load-balancer-api-external: resolved host name ac958be462187409e9edf3b2fe038d0e-65d752e864c50dff.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T00:15:14Z" - latency: 5.68297ms message: 'load-balancer-api-external: tcp connection to ac958be462187409e9edf3b2fe038d0e-65d752e864c50dff.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T00:14:14Z" - latency: 7.334753ms message: 'load-balancer-api-external: resolved host name ac958be462187409e9edf3b2fe038d0e-65d752e864c50dff.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T00:14:14Z" - latency: 4.763682ms message: 'load-balancer-api-external: tcp connection to ac958be462187409e9edf3b2fe038d0e-65d752e864c50dff.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T00:13:14Z" - latency: 6.711054ms message: 'load-balancer-api-external: resolved host name ac958be462187409e9edf3b2fe038d0e-65d752e864c50dff.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T00:13:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T00:05:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-78-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-78.ec2.internal uid: 947db32b-493e-4a65-8fcc-66b3e6f82525 resourceVersion: "30698" uid: 4a8106a5-4915-48e2-a820-225eaaddf329 spec: sourcePod: network-check-source-dbd9cf844-j2ptb targetEndpoint: ac958be462187409e9edf3b2fe038d0e-65d752e864c50dff.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-09T00:11:14Z" message: 'load-balancer-api-internal: tcp connection to ac958be462187409e9edf3b2fe038d0e-65d752e864c50dff.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.783919ms message: 'load-balancer-api-internal: tcp connection to ac958be462187409e9edf3b2fe038d0e-65d752e864c50dff.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T00:17:14Z" - latency: 6.427914ms message: 'load-balancer-api-internal: resolved host name ac958be462187409e9edf3b2fe038d0e-65d752e864c50dff.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T00:17:14Z" - latency: 3.962943ms message: 'load-balancer-api-internal: tcp connection to ac958be462187409e9edf3b2fe038d0e-65d752e864c50dff.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T00:16:14Z" - latency: 7.14465ms message: 'load-balancer-api-internal: resolved host name ac958be462187409e9edf3b2fe038d0e-65d752e864c50dff.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T00:16:14Z" - latency: 4.816029ms message: 'load-balancer-api-internal: tcp connection to ac958be462187409e9edf3b2fe038d0e-65d752e864c50dff.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T00:15:14Z" - latency: 6.95865ms message: 'load-balancer-api-internal: resolved host name ac958be462187409e9edf3b2fe038d0e-65d752e864c50dff.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T00:15:14Z" - latency: 5.711919ms message: 'load-balancer-api-internal: tcp connection to ac958be462187409e9edf3b2fe038d0e-65d752e864c50dff.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T00:14:14Z" - latency: 7.13736ms message: 'load-balancer-api-internal: resolved host name ac958be462187409e9edf3b2fe038d0e-65d752e864c50dff.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T00:14:14Z" - latency: 5.70067ms message: 'load-balancer-api-internal: tcp connection to ac958be462187409e9edf3b2fe038d0e-65d752e864c50dff.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T00:13:14Z" - latency: 6.698391ms message: 'load-balancer-api-internal: resolved host name ac958be462187409e9edf3b2fe038d0e-65d752e864c50dff.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T00:13:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T00:05:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-78-to-network-check-target-ip-10-0-128-73 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-78.ec2.internal uid: 947db32b-493e-4a65-8fcc-66b3e6f82525 resourceVersion: "25363" uid: 57395dc4-1738-4a8d-9d31-d906c0e39d6e spec: sourcePod: network-check-source-dbd9cf844-j2ptb targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-09T00:12:14Z" message: 'network-check-target-ip-10-0-128-73: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.648112ms message: 'network-check-target-ip-10-0-128-73: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T00:12:14Z" - latency: 1.762626ms message: 'network-check-target-ip-10-0-128-73: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T00:11:14Z" - latency: 1.934235ms message: 'network-check-target-ip-10-0-128-73: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T00:10:14Z" - latency: 1.949461ms message: 'network-check-target-ip-10-0-128-73: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T00:09:14Z" - latency: 1.94942ms message: 'network-check-target-ip-10-0-128-73: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T00:08:14Z" - latency: 1.620946ms message: 'network-check-target-ip-10-0-128-73: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T00:07:14Z" - latency: 2.116927ms message: 'network-check-target-ip-10-0-128-73: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T00:06:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T00:05:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-78-to-network-check-target-ip-10-0-129-4 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-78.ec2.internal uid: 947db32b-493e-4a65-8fcc-66b3e6f82525 resourceVersion: "25362" uid: b4bcb013-2e1b-437b-b784-e586d62fcb22 spec: sourcePod: network-check-source-dbd9cf844-j2ptb targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-09T00:12:14Z" message: 'network-check-target-ip-10-0-129-4: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.216126ms message: 'network-check-target-ip-10-0-129-4: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T00:12:14Z" - latency: 2.363062ms message: 'network-check-target-ip-10-0-129-4: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T00:11:14Z" - latency: 2.398424ms message: 'network-check-target-ip-10-0-129-4: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T00:10:14Z" - latency: 2.329419ms message: 'network-check-target-ip-10-0-129-4: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T00:09:14Z" - latency: 1.882352ms message: 'network-check-target-ip-10-0-129-4: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T00:08:14Z" - latency: 2.155822ms message: 'network-check-target-ip-10-0-129-4: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T00:07:14Z" - latency: 2.157868ms message: 'network-check-target-ip-10-0-129-4: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T00:06:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T00:05:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-78-to-network-check-target-ip-10-0-130-78 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-78.ec2.internal uid: 947db32b-493e-4a65-8fcc-66b3e6f82525 resourceVersion: "25361" uid: 42c4b626-7e77-4ad3-a930-aabe2881b81c spec: sourcePod: network-check-source-dbd9cf844-j2ptb targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-09T00:12:14Z" message: 'network-check-target-ip-10-0-130-78: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 842.577µs message: 'network-check-target-ip-10-0-130-78: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T00:12:14Z" - latency: 852.723µs message: 'network-check-target-ip-10-0-130-78: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T00:11:14Z" - latency: 1.164801ms message: 'network-check-target-ip-10-0-130-78: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T00:10:14Z" - latency: 859.172µs message: 'network-check-target-ip-10-0-130-78: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T00:09:14Z" - latency: 1.233854ms message: 'network-check-target-ip-10-0-130-78: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T00:08:14Z" - latency: 931.577µs message: 'network-check-target-ip-10-0-130-78: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T00:07:14Z" - latency: 1.25269ms message: 'network-check-target-ip-10-0-130-78: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T00:06:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T00:05:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-78-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-78.ec2.internal uid: 947db32b-493e-4a65-8fcc-66b3e6f82525 resourceVersion: "30697" uid: 17343d28-913f-4afc-b7b1-965ab0f15077 spec: sourcePod: network-check-source-dbd9cf844-j2ptb targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-09T00:11:14Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.085498ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T00:17:14Z" - latency: 1.801094ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T00:17:14Z" - latency: 1.280016ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T00:16:14Z" - latency: 1.63535ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T00:16:14Z" - latency: 834.848µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T00:15:14Z" - latency: 1.910742ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T00:15:14Z" - latency: 807.424µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T00:14:14Z" - latency: 2.391799ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T00:14:14Z" - latency: 936.947µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T00:13:14Z" - latency: 1.772699ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T00:13:14Z" kind: List metadata: resourceVersion: ""