apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T23:10:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-177-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-177.us-west-1.compute.internal uid: daebfde3-a062-47ee-af1b-25122ce27f74 resourceVersion: "113670" uid: 8acf2e65-a2d5-4c9c-b48d-fe7c543b3fcf spec: sourcePod: network-check-source-6f78d59f99-62rf9 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-10-30T23:17: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.245526ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:20:02Z" - latency: 1.2595ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:19:02Z" - latency: 945.578µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:18:02Z" - latency: 1.511772ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:17:02Z" - latency: 1.266542ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:16:02Z" - latency: 1.154843ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:15:02Z" - latency: 1.286892ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:14:02Z" - latency: 805.99µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:13:02Z" - latency: 984.312µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:12:02Z" - latency: 1.406738ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:11:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T23:10:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-177-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-177.us-west-1.compute.internal uid: daebfde3-a062-47ee-af1b-25122ce27f74 resourceVersion: "110861" uid: e81d27a2-8347-4388-a74b-8fee3c726605 spec: sourcePod: network-check-source-6f78d59f99-62rf9 targetEndpoint: a69c238be523043a7aa0939d4b6f2b19-5c317881c9fa0372.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T23:16:02Z" message: 'load-balancer-api-external: tcp connection to a69c238be523043a7aa0939d4b6f2b19-5c317881c9fa0372.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 53.847205ms message: 'load-balancer-api-external: tcp connection to a69c238be523043a7aa0939d4b6f2b19-5c317881c9fa0372.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:16:02Z" - latency: 7.722938ms message: 'load-balancer-api-external: resolved host name a69c238be523043a7aa0939d4b6f2b19-5c317881c9fa0372.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T00:16:02Z" - latency: 59.510266ms message: 'load-balancer-api-external: tcp connection to a69c238be523043a7aa0939d4b6f2b19-5c317881c9fa0372.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:15:02Z" - latency: 8.405976ms message: 'load-balancer-api-external: resolved host name a69c238be523043a7aa0939d4b6f2b19-5c317881c9fa0372.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T00:15:02Z" - latency: 55.173073ms message: 'load-balancer-api-external: tcp connection to a69c238be523043a7aa0939d4b6f2b19-5c317881c9fa0372.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:14:02Z" - latency: 9.413035ms message: 'load-balancer-api-external: resolved host name a69c238be523043a7aa0939d4b6f2b19-5c317881c9fa0372.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T00:14:02Z" - latency: 55.036163ms message: 'load-balancer-api-external: tcp connection to a69c238be523043a7aa0939d4b6f2b19-5c317881c9fa0372.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:13:02Z" - latency: 8.975097ms message: 'load-balancer-api-external: resolved host name a69c238be523043a7aa0939d4b6f2b19-5c317881c9fa0372.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T00:13:02Z" - latency: 53.85315ms message: 'load-balancer-api-external: tcp connection to a69c238be523043a7aa0939d4b6f2b19-5c317881c9fa0372.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:12:02Z" - latency: 9.893223ms message: 'load-balancer-api-external: resolved host name a69c238be523043a7aa0939d4b6f2b19-5c317881c9fa0372.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T00:12:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T23:10:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-177-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-177.us-west-1.compute.internal uid: daebfde3-a062-47ee-af1b-25122ce27f74 resourceVersion: "110860" uid: 8bcfcd2f-7844-4555-a037-b64b055efa63 spec: sourcePod: network-check-source-6f78d59f99-62rf9 targetEndpoint: a69c238be523043a7aa0939d4b6f2b19-5c317881c9fa0372.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T23:16:02Z" message: 'load-balancer-api-internal: tcp connection to a69c238be523043a7aa0939d4b6f2b19-5c317881c9fa0372.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 54.061329ms message: 'load-balancer-api-internal: tcp connection to a69c238be523043a7aa0939d4b6f2b19-5c317881c9fa0372.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:16:02Z" - latency: 7.7945ms message: 'load-balancer-api-internal: resolved host name a69c238be523043a7aa0939d4b6f2b19-5c317881c9fa0372.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T00:16:02Z" - latency: 55.474032ms message: 'load-balancer-api-internal: tcp connection to a69c238be523043a7aa0939d4b6f2b19-5c317881c9fa0372.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:15:02Z" - latency: 8.482816ms message: 'load-balancer-api-internal: resolved host name a69c238be523043a7aa0939d4b6f2b19-5c317881c9fa0372.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T00:15:02Z" - latency: 54.733805ms message: 'load-balancer-api-internal: tcp connection to a69c238be523043a7aa0939d4b6f2b19-5c317881c9fa0372.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:14:02Z" - latency: 9.52571ms message: 'load-balancer-api-internal: resolved host name a69c238be523043a7aa0939d4b6f2b19-5c317881c9fa0372.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T00:14:02Z" - latency: 55.119932ms message: 'load-balancer-api-internal: tcp connection to a69c238be523043a7aa0939d4b6f2b19-5c317881c9fa0372.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:13:02Z" - latency: 9.000361ms message: 'load-balancer-api-internal: resolved host name a69c238be523043a7aa0939d4b6f2b19-5c317881c9fa0372.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T00:13:02Z" - latency: 53.854038ms message: 'load-balancer-api-internal: tcp connection to a69c238be523043a7aa0939d4b6f2b19-5c317881c9fa0372.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:12:02Z" - latency: 9.82323ms message: 'load-balancer-api-internal: resolved host name a69c238be523043a7aa0939d4b6f2b19-5c317881c9fa0372.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T00:12:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T23:10:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-177-to-network-check-target-ip-10-0-130-177 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-177.us-west-1.compute.internal uid: daebfde3-a062-47ee-af1b-25122ce27f74 resourceVersion: "113666" uid: 3ac337f0-1084-48b0-a394-e8d1e6419418 spec: sourcePod: network-check-source-6f78d59f99-62rf9 targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-10-30T23:17:02Z" message: 'network-check-target-ip-10-0-130-177: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.406949ms message: 'network-check-target-ip-10-0-130-177: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:20:02Z" - latency: 1.004236ms message: 'network-check-target-ip-10-0-130-177: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:19:02Z" - latency: 1.504754ms message: 'network-check-target-ip-10-0-130-177: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:18:02Z" - latency: 1.00408ms message: 'network-check-target-ip-10-0-130-177: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:17:02Z" - latency: 1.055512ms message: 'network-check-target-ip-10-0-130-177: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:16:02Z" - latency: 1.035861ms message: 'network-check-target-ip-10-0-130-177: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:15:02Z" - latency: 1.062259ms message: 'network-check-target-ip-10-0-130-177: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:14:02Z" - latency: 820.092µs message: 'network-check-target-ip-10-0-130-177: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:13:02Z" - latency: 1.239022ms message: 'network-check-target-ip-10-0-130-177: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:12:02Z" - latency: 1.063586ms message: 'network-check-target-ip-10-0-130-177: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:11:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T23:10:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-177-to-network-check-target-ip-10-0-130-205 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-177.us-west-1.compute.internal uid: daebfde3-a062-47ee-af1b-25122ce27f74 resourceVersion: "113668" uid: ee7e22db-8c2b-4070-913c-78c9237221e0 spec: sourcePod: network-check-source-6f78d59f99-62rf9 targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-10-30T23:17:02Z" message: 'network-check-target-ip-10-0-130-205: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.16172ms message: 'network-check-target-ip-10-0-130-205: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:20:02Z" - latency: 2.249304ms message: 'network-check-target-ip-10-0-130-205: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:19:02Z" - latency: 2.47268ms message: 'network-check-target-ip-10-0-130-205: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:18:02Z" - latency: 2.300628ms message: 'network-check-target-ip-10-0-130-205: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:17:02Z" - latency: 2.393392ms message: 'network-check-target-ip-10-0-130-205: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:16:02Z" - latency: 2.228782ms message: 'network-check-target-ip-10-0-130-205: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:15:02Z" - latency: 2.647211ms message: 'network-check-target-ip-10-0-130-205: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:14:02Z" - latency: 2.381916ms message: 'network-check-target-ip-10-0-130-205: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:13:02Z" - latency: 2.258241ms message: 'network-check-target-ip-10-0-130-205: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:12:02Z" - latency: 1.950828ms message: 'network-check-target-ip-10-0-130-205: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:11:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T23:10:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-177-to-network-check-target-ip-10-0-133-110 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-177.us-west-1.compute.internal uid: daebfde3-a062-47ee-af1b-25122ce27f74 resourceVersion: "113669" uid: e81e5021-91a6-44e0-85ac-171cc12fb2c6 spec: sourcePod: network-check-source-6f78d59f99-62rf9 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-10-30T23:17:02Z" message: 'network-check-target-ip-10-0-133-110: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.206339ms message: 'network-check-target-ip-10-0-133-110: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:20:02Z" - latency: 2.216172ms message: 'network-check-target-ip-10-0-133-110: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:19:02Z" - latency: 1.693103ms message: 'network-check-target-ip-10-0-133-110: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:18:02Z" - latency: 2.315104ms message: 'network-check-target-ip-10-0-133-110: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:17:02Z" - latency: 2.294564ms message: 'network-check-target-ip-10-0-133-110: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:16:02Z" - latency: 1.949303ms message: 'network-check-target-ip-10-0-133-110: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:15:02Z" - latency: 2.447441ms message: 'network-check-target-ip-10-0-133-110: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:14:02Z" - latency: 1.824681ms message: 'network-check-target-ip-10-0-133-110: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:13:02Z" - latency: 1.996189ms message: 'network-check-target-ip-10-0-133-110: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:12:02Z" - latency: 2.170431ms message: 'network-check-target-ip-10-0-133-110: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:11:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T23:10:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-177-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-177.us-west-1.compute.internal uid: daebfde3-a062-47ee-af1b-25122ce27f74 resourceVersion: "110857" uid: edc7bb85-338e-49c3-96e5-100cc9f720b9 spec: sourcePod: network-check-source-6f78d59f99-62rf9 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-10-30T23:16:02Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.308506ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:16:02Z" - latency: 1.951687ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T00:16:02Z" - latency: 920.583µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:15:02Z" - latency: 1.980601ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T00:15:02Z" - latency: 875.817µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:14:02Z" - latency: 1.913548ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T00:14:02Z" - latency: 1.138771ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:13:02Z" - latency: 1.921863ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T00:13:02Z" - latency: 708.187µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:12:02Z" - latency: 2.021434ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T00:12:02Z" kind: List metadata: resourceVersion: ""