apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T16:30:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-117-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-117.ec2.internal uid: 0388c916-9fec-4785-bcf3-f778f72a86d2 resourceVersion: "63325" uid: 5ab7eb88-6885-4832-8197-bf9416afe993 spec: sourcePod: network-check-source-7bc5b6bf85-sw2c5 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-21T16:37:17Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.161425ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:12:17Z" - latency: 1.213418ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:11:17Z" - latency: 1.048812ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:10:17Z" - latency: 1.115571ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:09:17Z" - latency: 1.086984ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:08:17Z" - latency: 1.077202ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:07:17Z" - latency: 1.271945ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:06:17Z" - latency: 915.706µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:05:17Z" - latency: 1.033505ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:04:17Z" - latency: 1.109954ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:03:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T16:30:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-117-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-117.ec2.internal uid: 0388c916-9fec-4785-bcf3-f778f72a86d2 resourceVersion: "63327" uid: ae62ff83-e41a-42f5-8e26-7a52367f1078 spec: sourcePod: network-check-source-7bc5b6bf85-sw2c5 targetEndpoint: a00c81ba48c15439f9609d28bbf3086c-51bc74822ba10db8.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-21T16:36:17Z" message: 'load-balancer-api-external: tcp connection to a00c81ba48c15439f9609d28bbf3086c-51bc74822ba10db8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.061015ms message: 'load-balancer-api-external: tcp connection to a00c81ba48c15439f9609d28bbf3086c-51bc74822ba10db8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:12:17Z" - latency: 7.212964ms message: 'load-balancer-api-external: resolved host name a00c81ba48c15439f9609d28bbf3086c-51bc74822ba10db8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T17:12:17Z" - latency: 3.653645ms message: 'load-balancer-api-external: tcp connection to a00c81ba48c15439f9609d28bbf3086c-51bc74822ba10db8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:11:17Z" - latency: 6.531413ms message: 'load-balancer-api-external: resolved host name a00c81ba48c15439f9609d28bbf3086c-51bc74822ba10db8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T17:11:17Z" - latency: 3.864437ms message: 'load-balancer-api-external: tcp connection to a00c81ba48c15439f9609d28bbf3086c-51bc74822ba10db8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:10:17Z" - latency: 6.596343ms message: 'load-balancer-api-external: resolved host name a00c81ba48c15439f9609d28bbf3086c-51bc74822ba10db8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T17:10:17Z" - latency: 4.501239ms message: 'load-balancer-api-external: tcp connection to a00c81ba48c15439f9609d28bbf3086c-51bc74822ba10db8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:09:17Z" - latency: 6.885024ms message: 'load-balancer-api-external: resolved host name a00c81ba48c15439f9609d28bbf3086c-51bc74822ba10db8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T17:09:17Z" - latency: 5.750447ms message: 'load-balancer-api-external: tcp connection to a00c81ba48c15439f9609d28bbf3086c-51bc74822ba10db8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:08:17Z" - latency: 7.100353ms message: 'load-balancer-api-external: resolved host name a00c81ba48c15439f9609d28bbf3086c-51bc74822ba10db8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T17:08:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T16:30:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-117-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-117.ec2.internal uid: 0388c916-9fec-4785-bcf3-f778f72a86d2 resourceVersion: "63326" uid: a0d0d339-39d5-4bef-9fe1-85e5d188458e spec: sourcePod: network-check-source-7bc5b6bf85-sw2c5 targetEndpoint: a00c81ba48c15439f9609d28bbf3086c-51bc74822ba10db8.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-21T16:36:17Z" message: 'load-balancer-api-internal: tcp connection to a00c81ba48c15439f9609d28bbf3086c-51bc74822ba10db8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.918004ms message: 'load-balancer-api-internal: tcp connection to a00c81ba48c15439f9609d28bbf3086c-51bc74822ba10db8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:12:17Z" - latency: 7.265097ms message: 'load-balancer-api-internal: resolved host name a00c81ba48c15439f9609d28bbf3086c-51bc74822ba10db8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T17:12:17Z" - latency: 3.631192ms message: 'load-balancer-api-internal: tcp connection to a00c81ba48c15439f9609d28bbf3086c-51bc74822ba10db8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:11:17Z" - latency: 6.558149ms message: 'load-balancer-api-internal: resolved host name a00c81ba48c15439f9609d28bbf3086c-51bc74822ba10db8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T17:11:17Z" - latency: 3.87302ms message: 'load-balancer-api-internal: tcp connection to a00c81ba48c15439f9609d28bbf3086c-51bc74822ba10db8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:10:17Z" - latency: 6.648484ms message: 'load-balancer-api-internal: resolved host name a00c81ba48c15439f9609d28bbf3086c-51bc74822ba10db8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T17:10:17Z" - latency: 4.515745ms message: 'load-balancer-api-internal: tcp connection to a00c81ba48c15439f9609d28bbf3086c-51bc74822ba10db8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:09:17Z" - latency: 6.859898ms message: 'load-balancer-api-internal: resolved host name a00c81ba48c15439f9609d28bbf3086c-51bc74822ba10db8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T17:09:17Z" - latency: 4.346914ms message: 'load-balancer-api-internal: tcp connection to a00c81ba48c15439f9609d28bbf3086c-51bc74822ba10db8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:08:17Z" - latency: 7.15554ms message: 'load-balancer-api-internal: resolved host name a00c81ba48c15439f9609d28bbf3086c-51bc74822ba10db8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T17:08:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T16:30:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-117-to-network-check-target-ip-10-0-130-171 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-117.ec2.internal uid: 0388c916-9fec-4785-bcf3-f778f72a86d2 resourceVersion: "63323" uid: 9cad093b-555d-4159-99a3-831e5c5916df spec: sourcePod: network-check-source-7bc5b6bf85-sw2c5 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-21T16:37:17Z" message: 'network-check-target-ip-10-0-130-171: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.383188ms message: 'network-check-target-ip-10-0-130-171: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:12:17Z" - latency: 2.184685ms message: 'network-check-target-ip-10-0-130-171: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:11:17Z" - latency: 2.62939ms message: 'network-check-target-ip-10-0-130-171: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:10:17Z" - latency: 2.733099ms message: 'network-check-target-ip-10-0-130-171: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:09:17Z" - latency: 2.010126ms message: 'network-check-target-ip-10-0-130-171: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:08:17Z" - latency: 2.512568ms message: 'network-check-target-ip-10-0-130-171: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:07:17Z" - latency: 2.652505ms message: 'network-check-target-ip-10-0-130-171: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:06:17Z" - latency: 2.458285ms message: 'network-check-target-ip-10-0-130-171: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:05:17Z" - latency: 2.439033ms message: 'network-check-target-ip-10-0-130-171: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:04:17Z" - latency: 2.314475ms message: 'network-check-target-ip-10-0-130-171: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:03:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T16:30:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-117-to-network-check-target-ip-10-0-130-54 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-117.ec2.internal uid: 0388c916-9fec-4785-bcf3-f778f72a86d2 resourceVersion: "63322" uid: ed92d872-9829-41be-aca3-6708772d6d6c spec: sourcePod: network-check-source-7bc5b6bf85-sw2c5 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-21T16:37:17Z" message: 'network-check-target-ip-10-0-130-54: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.247646ms message: 'network-check-target-ip-10-0-130-54: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:12:17Z" - latency: 1.986249ms message: 'network-check-target-ip-10-0-130-54: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:11:17Z" - latency: 2.341844ms message: 'network-check-target-ip-10-0-130-54: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:10:17Z" - latency: 2.288846ms message: 'network-check-target-ip-10-0-130-54: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:09:17Z" - latency: 2.270386ms message: 'network-check-target-ip-10-0-130-54: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:08:17Z" - latency: 1.908753ms message: 'network-check-target-ip-10-0-130-54: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:07:17Z" - latency: 2.488198ms message: 'network-check-target-ip-10-0-130-54: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:06:17Z" - latency: 2.2339ms message: 'network-check-target-ip-10-0-130-54: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:05:17Z" - latency: 2.430939ms message: 'network-check-target-ip-10-0-130-54: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:04:17Z" - latency: 1.88912ms message: 'network-check-target-ip-10-0-130-54: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:03:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T16:30:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-117-to-network-check-target-ip-10-0-136-117 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-117.ec2.internal uid: 0388c916-9fec-4785-bcf3-f778f72a86d2 resourceVersion: "63321" uid: 4aee6ef9-792c-4d19-ae7b-8d5a2e006839 spec: sourcePod: network-check-source-7bc5b6bf85-sw2c5 targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-21T16:37:17Z" message: 'network-check-target-ip-10-0-136-117: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 937.709µs message: 'network-check-target-ip-10-0-136-117: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:12:17Z" - latency: 885.797µs message: 'network-check-target-ip-10-0-136-117: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:11:17Z" - latency: 1.097692ms message: 'network-check-target-ip-10-0-136-117: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:10:17Z" - latency: 978.919µs message: 'network-check-target-ip-10-0-136-117: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:09:17Z" - latency: 856.165µs message: 'network-check-target-ip-10-0-136-117: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:08:17Z" - latency: 1.434846ms message: 'network-check-target-ip-10-0-136-117: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:07:17Z" - latency: 873.419µs message: 'network-check-target-ip-10-0-136-117: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:06:17Z" - latency: 1.076669ms message: 'network-check-target-ip-10-0-136-117: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:05:17Z" - latency: 1.018423ms message: 'network-check-target-ip-10-0-136-117: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:04:17Z" - latency: 1.137004ms message: 'network-check-target-ip-10-0-136-117: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:03:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T16:30:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-117-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-117.ec2.internal uid: 0388c916-9fec-4785-bcf3-f778f72a86d2 resourceVersion: "63324" uid: 7c49a127-88db-4b28-803c-b7ff01ab0a4a spec: sourcePod: network-check-source-7bc5b6bf85-sw2c5 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-21T16:36:17Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 924.686µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:12:17Z" - latency: 1.744708ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-21T17:12:17Z" - latency: 925.765µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:11:17Z" - latency: 1.608058ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-21T17:11:17Z" - latency: 855.73µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:10:17Z" - latency: 1.783568ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-21T17:10:17Z" - latency: 1.072465ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:09:17Z" - latency: 1.794103ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-21T17:09:17Z" - latency: 1.17959ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:08:17Z" - latency: 1.702385ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-21T17:08:17Z" kind: List metadata: resourceVersion: ""