apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T15:41:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-52-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-52.ec2.internal uid: 6b15824c-508e-4423-9303-6a5420f7adc3 resourceVersion: "40672" uid: c388e535-e91e-4620-981f-924ef9cec2f8 spec: sourcePod: network-check-source-7f44b6dd87-8qwhf targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-05-21T15:48:30Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 999.279µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:09:30Z" - latency: 951.228µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:08:30Z" - latency: 980.03µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:07:30Z" - latency: 905.246µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:06:30Z" - latency: 830.114µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:05:30Z" - latency: 917.161µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:04:30Z" - latency: 856.431µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:03:30Z" - latency: 734.968µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:02:30Z" - latency: 934.48µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:01:30Z" - latency: 930.804µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:00:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T15:41:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-52-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-52.ec2.internal uid: 6b15824c-508e-4423-9303-6a5420f7adc3 resourceVersion: "42466" uid: 50034ff5-9550-4a46-9a93-c65d18a89dab spec: sourcePod: network-check-source-7f44b6dd87-8qwhf targetEndpoint: a3b9ffe56c80b4ed788d923a5f86d8a1-08c6322a7dbc2263.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-21T15:47:30Z" message: 'load-balancer-api-external: tcp connection to a3b9ffe56c80b4ed788d923a5f86d8a1-08c6322a7dbc2263.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.654223ms message: 'load-balancer-api-external: tcp connection to a3b9ffe56c80b4ed788d923a5f86d8a1-08c6322a7dbc2263.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:11:30Z" - latency: 6.999277ms message: 'load-balancer-api-external: resolved host name a3b9ffe56c80b4ed788d923a5f86d8a1-08c6322a7dbc2263.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T16:11:30Z" - latency: 5.014923ms message: 'load-balancer-api-external: tcp connection to a3b9ffe56c80b4ed788d923a5f86d8a1-08c6322a7dbc2263.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:10:30Z" - latency: 7.602143ms message: 'load-balancer-api-external: resolved host name a3b9ffe56c80b4ed788d923a5f86d8a1-08c6322a7dbc2263.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T16:10:30Z" - latency: 5.313726ms message: 'load-balancer-api-external: tcp connection to a3b9ffe56c80b4ed788d923a5f86d8a1-08c6322a7dbc2263.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:09:30Z" - latency: 7.550664ms message: 'load-balancer-api-external: resolved host name a3b9ffe56c80b4ed788d923a5f86d8a1-08c6322a7dbc2263.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T16:09:30Z" - latency: 3.482056ms message: 'load-balancer-api-external: tcp connection to a3b9ffe56c80b4ed788d923a5f86d8a1-08c6322a7dbc2263.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:08:30Z" - latency: 7.797487ms message: 'load-balancer-api-external: resolved host name a3b9ffe56c80b4ed788d923a5f86d8a1-08c6322a7dbc2263.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T16:08:30Z" - latency: 5.703621ms message: 'load-balancer-api-external: tcp connection to a3b9ffe56c80b4ed788d923a5f86d8a1-08c6322a7dbc2263.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:07:30Z" - latency: 7.595708ms message: 'load-balancer-api-external: resolved host name a3b9ffe56c80b4ed788d923a5f86d8a1-08c6322a7dbc2263.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T16:07:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T15:41:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-52-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-52.ec2.internal uid: 6b15824c-508e-4423-9303-6a5420f7adc3 resourceVersion: "42465" uid: e7783fc4-9925-4a11-87df-37ac7c5f267e spec: sourcePod: network-check-source-7f44b6dd87-8qwhf targetEndpoint: a3b9ffe56c80b4ed788d923a5f86d8a1-08c6322a7dbc2263.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-21T15:47:30Z" message: 'load-balancer-api-internal: tcp connection to a3b9ffe56c80b4ed788d923a5f86d8a1-08c6322a7dbc2263.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.605552ms message: 'load-balancer-api-internal: tcp connection to a3b9ffe56c80b4ed788d923a5f86d8a1-08c6322a7dbc2263.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:11:30Z" - latency: 7.040488ms message: 'load-balancer-api-internal: resolved host name a3b9ffe56c80b4ed788d923a5f86d8a1-08c6322a7dbc2263.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T16:11:30Z" - latency: 5.27692ms message: 'load-balancer-api-internal: tcp connection to a3b9ffe56c80b4ed788d923a5f86d8a1-08c6322a7dbc2263.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:10:30Z" - latency: 7.641219ms message: 'load-balancer-api-internal: resolved host name a3b9ffe56c80b4ed788d923a5f86d8a1-08c6322a7dbc2263.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T16:10:30Z" - latency: 3.314203ms message: 'load-balancer-api-internal: tcp connection to a3b9ffe56c80b4ed788d923a5f86d8a1-08c6322a7dbc2263.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:09:30Z" - latency: 7.658741ms message: 'load-balancer-api-internal: resolved host name a3b9ffe56c80b4ed788d923a5f86d8a1-08c6322a7dbc2263.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T16:09:30Z" - latency: 3.300543ms message: 'load-balancer-api-internal: tcp connection to a3b9ffe56c80b4ed788d923a5f86d8a1-08c6322a7dbc2263.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:08:30Z" - latency: 7.768459ms message: 'load-balancer-api-internal: resolved host name a3b9ffe56c80b4ed788d923a5f86d8a1-08c6322a7dbc2263.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T16:08:30Z" - latency: 5.241547ms message: 'load-balancer-api-internal: tcp connection to a3b9ffe56c80b4ed788d923a5f86d8a1-08c6322a7dbc2263.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:07:30Z" - latency: 7.653938ms message: 'load-balancer-api-internal: resolved host name a3b9ffe56c80b4ed788d923a5f86d8a1-08c6322a7dbc2263.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T16:07:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T15:41:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-52-to-network-check-target-ip-10-0-129-52 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-52.ec2.internal uid: 6b15824c-508e-4423-9303-6a5420f7adc3 resourceVersion: "40669" uid: 702a9b69-0565-4c00-8885-bd37541b1115 spec: sourcePod: network-check-source-7f44b6dd87-8qwhf targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-21T15:48:30Z" message: 'network-check-target-ip-10-0-129-52: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 775.513µs message: 'network-check-target-ip-10-0-129-52: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:09:30Z" - latency: 1.252579ms message: 'network-check-target-ip-10-0-129-52: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:08:30Z" - latency: 1.095932ms message: 'network-check-target-ip-10-0-129-52: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:07:30Z" - latency: 839.486µs message: 'network-check-target-ip-10-0-129-52: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:06:30Z" - latency: 802.949µs message: 'network-check-target-ip-10-0-129-52: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:05:30Z" - latency: 1.094297ms message: 'network-check-target-ip-10-0-129-52: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:04:30Z" - latency: 747.294µs message: 'network-check-target-ip-10-0-129-52: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:03:30Z" - latency: 892.556µs message: 'network-check-target-ip-10-0-129-52: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:02:30Z" - latency: 811.043µs message: 'network-check-target-ip-10-0-129-52: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:01:30Z" - latency: 1.129354ms message: 'network-check-target-ip-10-0-129-52: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:00:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T15:41:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-52-to-network-check-target-ip-10-0-136-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-52.ec2.internal uid: 6b15824c-508e-4423-9303-6a5420f7adc3 resourceVersion: "40671" uid: 4fa8381c-4c1c-4488-90f5-51b7f165dc47 spec: sourcePod: network-check-source-7f44b6dd87-8qwhf targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-21T15:48:30Z" message: 'network-check-target-ip-10-0-136-0: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.020699ms message: 'network-check-target-ip-10-0-136-0: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:09:30Z" - latency: 2.023099ms message: 'network-check-target-ip-10-0-136-0: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:08:30Z" - latency: 2.163218ms message: 'network-check-target-ip-10-0-136-0: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:07:30Z" - latency: 1.971634ms message: 'network-check-target-ip-10-0-136-0: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:06:30Z" - latency: 1.588083ms message: 'network-check-target-ip-10-0-136-0: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:05:30Z" - latency: 2.381213ms message: 'network-check-target-ip-10-0-136-0: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:04:30Z" - latency: 2.016103ms message: 'network-check-target-ip-10-0-136-0: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:03:30Z" - latency: 2.381708ms message: 'network-check-target-ip-10-0-136-0: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:02:30Z" - latency: 2.090599ms message: 'network-check-target-ip-10-0-136-0: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:01:30Z" - latency: 2.439835ms message: 'network-check-target-ip-10-0-136-0: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:00:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T15:41:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-52-to-network-check-target-ip-10-0-136-55 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-52.ec2.internal uid: 6b15824c-508e-4423-9303-6a5420f7adc3 resourceVersion: "40670" uid: b3bca6e8-46e3-4267-91f0-1f8cb484fba5 spec: sourcePod: network-check-source-7f44b6dd87-8qwhf targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-05-21T15:48:30Z" message: 'network-check-target-ip-10-0-136-55: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.170689ms message: 'network-check-target-ip-10-0-136-55: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:09:30Z" - latency: 2.193139ms message: 'network-check-target-ip-10-0-136-55: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:08:30Z" - latency: 2.320763ms message: 'network-check-target-ip-10-0-136-55: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:07:30Z" - latency: 2.137364ms message: 'network-check-target-ip-10-0-136-55: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:06:30Z" - latency: 2.042227ms message: 'network-check-target-ip-10-0-136-55: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:05:30Z" - latency: 2.49726ms message: 'network-check-target-ip-10-0-136-55: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:04:30Z" - latency: 2.225001ms message: 'network-check-target-ip-10-0-136-55: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:03:30Z" - latency: 2.374817ms message: 'network-check-target-ip-10-0-136-55: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:02:30Z" - latency: 2.233978ms message: 'network-check-target-ip-10-0-136-55: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:01:30Z" - latency: 2.599984ms message: 'network-check-target-ip-10-0-136-55: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:00:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T15:41:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-52-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-52.ec2.internal uid: 6b15824c-508e-4423-9303-6a5420f7adc3 resourceVersion: "42464" uid: 57e73d07-ab71-4a5c-914a-8235d8677276 spec: sourcePod: network-check-source-7f44b6dd87-8qwhf targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-05-21T15:47:30Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 859.954µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:11:30Z" - latency: 1.625141ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-21T16:11:30Z" - latency: 985.053µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:10:30Z" - latency: 1.674044ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-21T16:10:30Z" - latency: 724.074µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:09:30Z" - latency: 1.638831ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-21T16:09:30Z" - latency: 1.176923ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:08:30Z" - latency: 1.745328ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-21T16:08:30Z" - latency: 1.033997ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:07:30Z" - latency: 1.807987ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-21T16:07:30Z" kind: List metadata: resourceVersion: ""