apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T21:30:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-201-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-201.ec2.internal uid: f8ea8074-54e8-4e40-a72f-d9c303b17720 resourceVersion: "31526" uid: 2d0ddcf2-7e12-4b65-a14e-2fdbcd06181c spec: sourcePod: network-check-source-8894fc9bd-vlq8x targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-24T21:37:01Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 890.28µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:12:01Z" - latency: 1.084685ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:11:01Z" - latency: 1.027337ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:10:01Z" - latency: 1.160129ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:09:01Z" - latency: 781.645µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:08:01Z" - latency: 867.863µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:07:01Z" - latency: 947.927µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:06:01Z" - latency: 1.029659ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:05:01Z" - latency: 1.002501ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:04:01Z" - latency: 1.040268ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:03:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T21:30:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-201-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-201.ec2.internal uid: f8ea8074-54e8-4e40-a72f-d9c303b17720 resourceVersion: "31527" uid: 4d42bdf9-3317-4cbb-a613-ba585e4bb5ea spec: sourcePod: network-check-source-8894fc9bd-vlq8x targetEndpoint: a3c8bba5684d248528f073edf5fdfc90-6bff454f2b5bd216.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-24T21:36:01Z" message: 'load-balancer-api-external: tcp connection to a3c8bba5684d248528f073edf5fdfc90-6bff454f2b5bd216.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.735919ms message: 'load-balancer-api-external: tcp connection to a3c8bba5684d248528f073edf5fdfc90-6bff454f2b5bd216.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:12:01Z" - latency: 8.060398ms message: 'load-balancer-api-external: resolved host name a3c8bba5684d248528f073edf5fdfc90-6bff454f2b5bd216.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T22:12:01Z" - latency: 5.162739ms message: 'load-balancer-api-external: tcp connection to a3c8bba5684d248528f073edf5fdfc90-6bff454f2b5bd216.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:11:01Z" - latency: 8.039461ms message: 'load-balancer-api-external: resolved host name a3c8bba5684d248528f073edf5fdfc90-6bff454f2b5bd216.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T22:11:01Z" - latency: 4.778803ms message: 'load-balancer-api-external: tcp connection to a3c8bba5684d248528f073edf5fdfc90-6bff454f2b5bd216.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:10:01Z" - latency: 8.574007ms message: 'load-balancer-api-external: resolved host name a3c8bba5684d248528f073edf5fdfc90-6bff454f2b5bd216.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T22:10:01Z" - latency: 4.102681ms message: 'load-balancer-api-external: tcp connection to a3c8bba5684d248528f073edf5fdfc90-6bff454f2b5bd216.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:09:01Z" - latency: 7.990443ms message: 'load-balancer-api-external: resolved host name a3c8bba5684d248528f073edf5fdfc90-6bff454f2b5bd216.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T22:09:01Z" - latency: 6.680232ms message: 'load-balancer-api-external: tcp connection to a3c8bba5684d248528f073edf5fdfc90-6bff454f2b5bd216.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:08:01Z" - latency: 9.811063ms message: 'load-balancer-api-external: resolved host name a3c8bba5684d248528f073edf5fdfc90-6bff454f2b5bd216.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T22:08:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T21:30:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-201-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-201.ec2.internal uid: f8ea8074-54e8-4e40-a72f-d9c303b17720 resourceVersion: "31528" uid: c43d17a1-5142-4efb-8203-2dce42f80e31 spec: sourcePod: network-check-source-8894fc9bd-vlq8x targetEndpoint: a3c8bba5684d248528f073edf5fdfc90-6bff454f2b5bd216.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-24T21:36:01Z" message: 'load-balancer-api-internal: tcp connection to a3c8bba5684d248528f073edf5fdfc90-6bff454f2b5bd216.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.731665ms message: 'load-balancer-api-internal: tcp connection to a3c8bba5684d248528f073edf5fdfc90-6bff454f2b5bd216.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:12:01Z" - latency: 7.9877ms message: 'load-balancer-api-internal: resolved host name a3c8bba5684d248528f073edf5fdfc90-6bff454f2b5bd216.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T22:12:01Z" - latency: 5.131653ms message: 'load-balancer-api-internal: tcp connection to a3c8bba5684d248528f073edf5fdfc90-6bff454f2b5bd216.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:11:01Z" - latency: 8.172773ms message: 'load-balancer-api-internal: resolved host name a3c8bba5684d248528f073edf5fdfc90-6bff454f2b5bd216.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T22:11:01Z" - latency: 4.746777ms message: 'load-balancer-api-internal: tcp connection to a3c8bba5684d248528f073edf5fdfc90-6bff454f2b5bd216.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:10:01Z" - latency: 8.619396ms message: 'load-balancer-api-internal: resolved host name a3c8bba5684d248528f073edf5fdfc90-6bff454f2b5bd216.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T22:10:01Z" - latency: 5.17232ms message: 'load-balancer-api-internal: tcp connection to a3c8bba5684d248528f073edf5fdfc90-6bff454f2b5bd216.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:09:01Z" - latency: 8.01843ms message: 'load-balancer-api-internal: resolved host name a3c8bba5684d248528f073edf5fdfc90-6bff454f2b5bd216.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T22:09:01Z" - latency: 5.314905ms message: 'load-balancer-api-internal: tcp connection to a3c8bba5684d248528f073edf5fdfc90-6bff454f2b5bd216.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:08:01Z" - latency: 9.73641ms message: 'load-balancer-api-internal: resolved host name a3c8bba5684d248528f073edf5fdfc90-6bff454f2b5bd216.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T22:08:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T21:30:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-201-to-network-check-target-ip-10-0-130-31 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-201.ec2.internal uid: f8ea8074-54e8-4e40-a72f-d9c303b17720 resourceVersion: "31523" uid: 971325af-09aa-49b3-8a47-6db9d3fb12cb spec: sourcePod: network-check-source-8894fc9bd-vlq8x targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-04-24T21:37:01Z" message: 'network-check-target-ip-10-0-130-31: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.267003ms message: 'network-check-target-ip-10-0-130-31: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:12:01Z" - latency: 1.982131ms message: 'network-check-target-ip-10-0-130-31: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:11:01Z" - latency: 1.987626ms message: 'network-check-target-ip-10-0-130-31: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:10:01Z" - latency: 2.008978ms message: 'network-check-target-ip-10-0-130-31: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:09:01Z" - latency: 1.757825ms message: 'network-check-target-ip-10-0-130-31: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:08:01Z" - latency: 1.902005ms message: 'network-check-target-ip-10-0-130-31: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:07:01Z" - latency: 1.907878ms message: 'network-check-target-ip-10-0-130-31: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:06:01Z" - latency: 1.982262ms message: 'network-check-target-ip-10-0-130-31: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:05:01Z" - latency: 1.942268ms message: 'network-check-target-ip-10-0-130-31: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:04:01Z" - latency: 2.102519ms message: 'network-check-target-ip-10-0-130-31: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:03:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T21:30:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-201-to-network-check-target-ip-10-0-132-124 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-201.ec2.internal uid: f8ea8074-54e8-4e40-a72f-d9c303b17720 resourceVersion: "31524" uid: 6ff04cfb-b51f-4fe7-b761-064e0be9df7b spec: sourcePod: network-check-source-8894fc9bd-vlq8x targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-24T21:37:01Z" message: 'network-check-target-ip-10-0-132-124: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.208291ms message: 'network-check-target-ip-10-0-132-124: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:12:01Z" - latency: 2.206904ms message: 'network-check-target-ip-10-0-132-124: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:11:01Z" - latency: 2.378005ms message: 'network-check-target-ip-10-0-132-124: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:10:01Z" - latency: 2.054826ms message: 'network-check-target-ip-10-0-132-124: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:09:01Z" - latency: 1.764054ms message: 'network-check-target-ip-10-0-132-124: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:08:01Z" - latency: 2.270259ms message: 'network-check-target-ip-10-0-132-124: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:07:01Z" - latency: 1.936897ms message: 'network-check-target-ip-10-0-132-124: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:06:01Z" - latency: 2.13018ms message: 'network-check-target-ip-10-0-132-124: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:05:01Z" - latency: 1.833249ms message: 'network-check-target-ip-10-0-132-124: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:04:01Z" - latency: 2.147898ms message: 'network-check-target-ip-10-0-132-124: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:03:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T21:30:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-201-to-network-check-target-ip-10-0-136-201 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-201.ec2.internal uid: f8ea8074-54e8-4e40-a72f-d9c303b17720 resourceVersion: "31522" uid: 5afc1ddd-8276-4661-92d9-346456095fa4 spec: sourcePod: network-check-source-8894fc9bd-vlq8x targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-04-24T21:37:01Z" message: 'network-check-target-ip-10-0-136-201: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 875.598µs message: 'network-check-target-ip-10-0-136-201: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:12:01Z" - latency: 857.554µs message: 'network-check-target-ip-10-0-136-201: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:11:01Z" - latency: 994.689µs message: 'network-check-target-ip-10-0-136-201: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:10:01Z" - latency: 729.223µs message: 'network-check-target-ip-10-0-136-201: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:09:01Z" - latency: 813.684µs message: 'network-check-target-ip-10-0-136-201: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:08:01Z" - latency: 938.331µs message: 'network-check-target-ip-10-0-136-201: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:07:01Z" - latency: 1.054143ms message: 'network-check-target-ip-10-0-136-201: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:06:01Z" - latency: 866.034µs message: 'network-check-target-ip-10-0-136-201: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:05:01Z" - latency: 878.849µs message: 'network-check-target-ip-10-0-136-201: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:04:01Z" - latency: 914.459µs message: 'network-check-target-ip-10-0-136-201: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:03:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T21:30:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-201-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-201.ec2.internal uid: f8ea8074-54e8-4e40-a72f-d9c303b17720 resourceVersion: "31525" uid: ddf06e80-6429-448c-8465-b591b08e2d58 spec: sourcePod: network-check-source-8894fc9bd-vlq8x targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-24T21:36:01Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.02997ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:12:01Z" - latency: 1.846074ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T22:12:01Z" - latency: 721.476µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:11:01Z" - latency: 1.677833ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T22:11:01Z" - latency: 973.342µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:10:01Z" - latency: 1.598431ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T22:10:01Z" - latency: 1.264004ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:09:01Z" - latency: 1.666619ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T22:09:01Z" - latency: 764.508µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:08:01Z" - latency: 1.760512ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T22:08:01Z" kind: List metadata: resourceVersion: ""