apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-13T07:15:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-188-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-188.ec2.internal uid: 8b837f0a-bd14-45c6-bd46-1f40d00bbc47 resourceVersion: "54475" uid: dfcc15e5-57ae-4aef-8e81-5824d4c29075 spec: sourcePod: network-check-source-869dcfcdcd-l8ggl targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-13T07:22:02Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.097562ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T07:50:02Z" - latency: 983.752µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T07:49:02Z" - latency: 2.008737ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T07:48:02Z" - latency: 1.710669ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T07:47:02Z" - latency: 1.198864ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T07:46:02Z" - latency: 1.137072ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T07:45:02Z" - latency: 1.352367ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T07:44:02Z" - latency: 1.216992ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T07:43:02Z" - latency: 1.272399ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T07:42:02Z" - latency: 1.364951ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T07:41:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-13T07:15:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-188-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-188.ec2.internal uid: 8b837f0a-bd14-45c6-bd46-1f40d00bbc47 resourceVersion: "55474" uid: 49ab06e3-bf73-491e-a48d-4e51fedcb1bb spec: sourcePod: network-check-source-869dcfcdcd-l8ggl targetEndpoint: a45c6f2e50e524360a6939580eef3bde-7a2af00c8999c9ef.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-13T07:21:02Z" message: 'load-balancer-api-external: tcp connection to a45c6f2e50e524360a6939580eef3bde-7a2af00c8999c9ef.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.618946ms message: 'load-balancer-api-external: tcp connection to a45c6f2e50e524360a6939580eef3bde-7a2af00c8999c9ef.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T07:51:02Z" - latency: 9.365313ms message: 'load-balancer-api-external: resolved host name a45c6f2e50e524360a6939580eef3bde-7a2af00c8999c9ef.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T07:51:02Z" - latency: 7.651678ms message: 'load-balancer-api-external: tcp connection to a45c6f2e50e524360a6939580eef3bde-7a2af00c8999c9ef.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T07:50:02Z" - latency: 7.598162ms message: 'load-balancer-api-external: resolved host name a45c6f2e50e524360a6939580eef3bde-7a2af00c8999c9ef.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T07:50:02Z" - latency: 5.413414ms message: 'load-balancer-api-external: tcp connection to a45c6f2e50e524360a6939580eef3bde-7a2af00c8999c9ef.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T07:49:02Z" - latency: 10.572552ms message: 'load-balancer-api-external: resolved host name a45c6f2e50e524360a6939580eef3bde-7a2af00c8999c9ef.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T07:49:02Z" - latency: 4.07471ms message: 'load-balancer-api-external: tcp connection to a45c6f2e50e524360a6939580eef3bde-7a2af00c8999c9ef.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T07:48:02Z" - latency: 7.46356ms message: 'load-balancer-api-external: resolved host name a45c6f2e50e524360a6939580eef3bde-7a2af00c8999c9ef.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T07:48:02Z" - latency: 3.931253ms message: 'load-balancer-api-external: tcp connection to a45c6f2e50e524360a6939580eef3bde-7a2af00c8999c9ef.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T07:47:02Z" - latency: 7.311286ms message: 'load-balancer-api-external: resolved host name a45c6f2e50e524360a6939580eef3bde-7a2af00c8999c9ef.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T07:47:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-13T07:15:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-188-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-188.ec2.internal uid: 8b837f0a-bd14-45c6-bd46-1f40d00bbc47 resourceVersion: "55475" uid: d44bfe72-651f-4d59-8521-85192940310d spec: sourcePod: network-check-source-869dcfcdcd-l8ggl targetEndpoint: a45c6f2e50e524360a6939580eef3bde-7a2af00c8999c9ef.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-13T07:21:02Z" message: 'load-balancer-api-internal: tcp connection to a45c6f2e50e524360a6939580eef3bde-7a2af00c8999c9ef.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.597148ms message: 'load-balancer-api-internal: tcp connection to a45c6f2e50e524360a6939580eef3bde-7a2af00c8999c9ef.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T07:51:02Z" - latency: 9.434363ms message: 'load-balancer-api-internal: resolved host name a45c6f2e50e524360a6939580eef3bde-7a2af00c8999c9ef.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T07:51:02Z" - latency: 7.611175ms message: 'load-balancer-api-internal: tcp connection to a45c6f2e50e524360a6939580eef3bde-7a2af00c8999c9ef.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T07:50:02Z" - latency: 7.759821ms message: 'load-balancer-api-internal: resolved host name a45c6f2e50e524360a6939580eef3bde-7a2af00c8999c9ef.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T07:50:02Z" - latency: 4.608579ms message: 'load-balancer-api-internal: tcp connection to a45c6f2e50e524360a6939580eef3bde-7a2af00c8999c9ef.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T07:49:02Z" - latency: 10.475184ms message: 'load-balancer-api-internal: resolved host name a45c6f2e50e524360a6939580eef3bde-7a2af00c8999c9ef.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T07:49:02Z" - latency: 4.061107ms message: 'load-balancer-api-internal: tcp connection to a45c6f2e50e524360a6939580eef3bde-7a2af00c8999c9ef.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T07:48:02Z" - latency: 7.325281ms message: 'load-balancer-api-internal: resolved host name a45c6f2e50e524360a6939580eef3bde-7a2af00c8999c9ef.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T07:48:02Z" - latency: 3.886783ms message: 'load-balancer-api-internal: tcp connection to a45c6f2e50e524360a6939580eef3bde-7a2af00c8999c9ef.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T07:47:02Z" - latency: 7.429525ms message: 'load-balancer-api-internal: resolved host name a45c6f2e50e524360a6939580eef3bde-7a2af00c8999c9ef.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T07:47:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-13T07:15:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-188-to-network-check-target-ip-10-0-130-143 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-188.ec2.internal uid: 8b837f0a-bd14-45c6-bd46-1f40d00bbc47 resourceVersion: "54472" uid: 8b7c1248-2bfb-44c7-9d78-efcd4b0d889c spec: sourcePod: network-check-source-869dcfcdcd-l8ggl targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-13T07:22:02Z" message: 'network-check-target-ip-10-0-130-143: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.793453ms message: 'network-check-target-ip-10-0-130-143: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T07:50:02Z" - latency: 1.921999ms message: 'network-check-target-ip-10-0-130-143: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T07:49:02Z" - latency: 1.521521ms message: 'network-check-target-ip-10-0-130-143: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T07:48:02Z" - latency: 1.915785ms message: 'network-check-target-ip-10-0-130-143: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T07:47:02Z" - latency: 1.781898ms message: 'network-check-target-ip-10-0-130-143: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T07:46:02Z" - latency: 2.041725ms message: 'network-check-target-ip-10-0-130-143: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T07:45:02Z" - latency: 1.832775ms message: 'network-check-target-ip-10-0-130-143: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T07:44:02Z" - latency: 1.626126ms message: 'network-check-target-ip-10-0-130-143: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T07:43:02Z" - latency: 1.584466ms message: 'network-check-target-ip-10-0-130-143: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T07:42:02Z" - latency: 1.923942ms message: 'network-check-target-ip-10-0-130-143: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T07:41:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-13T07:15:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-188-to-network-check-target-ip-10-0-132-188 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-188.ec2.internal uid: 8b837f0a-bd14-45c6-bd46-1f40d00bbc47 resourceVersion: "54473" uid: 5ff1cbb7-3cce-48b3-af3b-988df9b5fe73 spec: sourcePod: network-check-source-869dcfcdcd-l8ggl targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-13T07:22:02Z" message: 'network-check-target-ip-10-0-132-188: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 893.545µs message: 'network-check-target-ip-10-0-132-188: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T07:50:02Z" - latency: 1.615723ms message: 'network-check-target-ip-10-0-132-188: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T07:49:02Z" - latency: 787.634µs message: 'network-check-target-ip-10-0-132-188: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T07:48:02Z" - latency: 1.249611ms message: 'network-check-target-ip-10-0-132-188: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T07:47:02Z" - latency: 1.328998ms message: 'network-check-target-ip-10-0-132-188: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T07:46:02Z" - latency: 842.619µs message: 'network-check-target-ip-10-0-132-188: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T07:45:02Z" - latency: 869.569µs message: 'network-check-target-ip-10-0-132-188: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T07:44:02Z" - latency: 1.400311ms message: 'network-check-target-ip-10-0-132-188: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T07:43:02Z" - latency: 1.217117ms message: 'network-check-target-ip-10-0-132-188: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T07:42:02Z" - latency: 792.599µs message: 'network-check-target-ip-10-0-132-188: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T07:41:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-13T07:15:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-188-to-network-check-target-ip-10-0-141-197 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-188.ec2.internal uid: 8b837f0a-bd14-45c6-bd46-1f40d00bbc47 resourceVersion: "54474" uid: d07fc6f8-5e1b-456b-9b60-ca32e845c158 spec: sourcePod: network-check-source-869dcfcdcd-l8ggl targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-13T07:22:02Z" message: 'network-check-target-ip-10-0-141-197: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.323689ms message: 'network-check-target-ip-10-0-141-197: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T07:50:02Z" - latency: 2.471224ms message: 'network-check-target-ip-10-0-141-197: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T07:49:02Z" - latency: 2.98509ms message: 'network-check-target-ip-10-0-141-197: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T07:48:02Z" - latency: 2.140902ms message: 'network-check-target-ip-10-0-141-197: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T07:47:02Z" - latency: 1.975635ms message: 'network-check-target-ip-10-0-141-197: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T07:46:02Z" - latency: 1.974281ms message: 'network-check-target-ip-10-0-141-197: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T07:45:02Z" - latency: 2.346179ms message: 'network-check-target-ip-10-0-141-197: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T07:44:02Z" - latency: 2.694818ms message: 'network-check-target-ip-10-0-141-197: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T07:43:02Z" - latency: 2.251358ms message: 'network-check-target-ip-10-0-141-197: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T07:42:02Z" - latency: 1.929663ms message: 'network-check-target-ip-10-0-141-197: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T07:41:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-13T07:15:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-188-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-188.ec2.internal uid: 8b837f0a-bd14-45c6-bd46-1f40d00bbc47 resourceVersion: "55473" uid: 1e3b6dbd-451c-4a1c-b443-30541e707c4b spec: sourcePod: network-check-source-869dcfcdcd-l8ggl targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-13T07:21:02Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 727.818µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-13T07:51:02Z" - latency: 1.863709ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-13T07:51:02Z" - latency: 845.946µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-13T07:50:02Z" - latency: 2.565866ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-13T07:50:02Z" - latency: 1.200933ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-13T07:49:02Z" - latency: 2.349641ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-13T07:49:02Z" - latency: 877.22µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-13T07:48:02Z" - latency: 1.997973ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-13T07:48:02Z" - latency: 740.536µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-13T07:47:02Z" - latency: 2.219385ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-13T07:47:02Z" kind: List metadata: resourceVersion: ""