apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T10:12:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-249-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-249.ec2.internal uid: 30ef9b60-4917-4faf-90a7-7ac163f98dd0 resourceVersion: "25912" uid: a09e181f-3a26-4d02-b651-f53af8e67d9c spec: sourcePod: network-check-source-7d88cb55d8-svlqb targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-28T10:19:03Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 986.494µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:40:03Z" - latency: 932.483µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:39:03Z" - latency: 867.48µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:38:03Z" - latency: 876.796µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:37:03Z" - latency: 1.027839ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:36:03Z" - latency: 1.179276ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:35:03Z" - latency: 830.627µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:34:03Z" - latency: 979.523µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:33:03Z" - latency: 1.282893ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:32:03Z" - latency: 902.107µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:31:03Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T10:12:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-249-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-249.ec2.internal uid: 30ef9b60-4917-4faf-90a7-7ac163f98dd0 resourceVersion: "27017" uid: d6f23a15-0cf7-441f-b102-e7a81cbd520d spec: sourcePod: network-check-source-7d88cb55d8-svlqb targetEndpoint: af1ed198eaac04879a7497040a391120-cdd2b967bcd5983c.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-28T10:18:03Z" message: 'load-balancer-api-external: tcp connection to af1ed198eaac04879a7497040a391120-cdd2b967bcd5983c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.691984ms message: 'load-balancer-api-external: tcp connection to af1ed198eaac04879a7497040a391120-cdd2b967bcd5983c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:42:03Z" - latency: 8.083026ms message: 'load-balancer-api-external: resolved host name af1ed198eaac04879a7497040a391120-cdd2b967bcd5983c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T10:42:03Z" - latency: 4.290337ms message: 'load-balancer-api-external: tcp connection to af1ed198eaac04879a7497040a391120-cdd2b967bcd5983c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:41:03Z" - latency: 8.102742ms message: 'load-balancer-api-external: resolved host name af1ed198eaac04879a7497040a391120-cdd2b967bcd5983c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T10:41:03Z" - latency: 5.080794ms message: 'load-balancer-api-external: tcp connection to af1ed198eaac04879a7497040a391120-cdd2b967bcd5983c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:40:03Z" - latency: 7.654556ms message: 'load-balancer-api-external: resolved host name af1ed198eaac04879a7497040a391120-cdd2b967bcd5983c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T10:40:03Z" - latency: 4.790842ms message: 'load-balancer-api-external: tcp connection to af1ed198eaac04879a7497040a391120-cdd2b967bcd5983c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:39:03Z" - latency: 8.615031ms message: 'load-balancer-api-external: resolved host name af1ed198eaac04879a7497040a391120-cdd2b967bcd5983c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T10:39:03Z" - latency: 4.791695ms message: 'load-balancer-api-external: tcp connection to af1ed198eaac04879a7497040a391120-cdd2b967bcd5983c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:38:03Z" - latency: 7.558054ms message: 'load-balancer-api-external: resolved host name af1ed198eaac04879a7497040a391120-cdd2b967bcd5983c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T10:38:03Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T10:12:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-249-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-249.ec2.internal uid: 30ef9b60-4917-4faf-90a7-7ac163f98dd0 resourceVersion: "27016" uid: 6ca8e34d-a28c-4863-8b8a-e02d286c5d11 spec: sourcePod: network-check-source-7d88cb55d8-svlqb targetEndpoint: af1ed198eaac04879a7497040a391120-cdd2b967bcd5983c.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-28T10:18:03Z" message: 'load-balancer-api-internal: tcp connection to af1ed198eaac04879a7497040a391120-cdd2b967bcd5983c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.828094ms message: 'load-balancer-api-internal: tcp connection to af1ed198eaac04879a7497040a391120-cdd2b967bcd5983c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:42:03Z" - latency: 8.007923ms message: 'load-balancer-api-internal: resolved host name af1ed198eaac04879a7497040a391120-cdd2b967bcd5983c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T10:42:03Z" - latency: 4.282865ms message: 'load-balancer-api-internal: tcp connection to af1ed198eaac04879a7497040a391120-cdd2b967bcd5983c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:41:03Z" - latency: 8.068695ms message: 'load-balancer-api-internal: resolved host name af1ed198eaac04879a7497040a391120-cdd2b967bcd5983c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T10:41:03Z" - latency: 5.400323ms message: 'load-balancer-api-internal: tcp connection to af1ed198eaac04879a7497040a391120-cdd2b967bcd5983c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:40:03Z" - latency: 7.73152ms message: 'load-balancer-api-internal: resolved host name af1ed198eaac04879a7497040a391120-cdd2b967bcd5983c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T10:40:03Z" - latency: 4.959734ms message: 'load-balancer-api-internal: tcp connection to af1ed198eaac04879a7497040a391120-cdd2b967bcd5983c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:39:03Z" - latency: 8.511858ms message: 'load-balancer-api-internal: resolved host name af1ed198eaac04879a7497040a391120-cdd2b967bcd5983c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T10:39:03Z" - latency: 4.658536ms message: 'load-balancer-api-internal: tcp connection to af1ed198eaac04879a7497040a391120-cdd2b967bcd5983c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:38:03Z" - latency: 7.632539ms message: 'load-balancer-api-internal: resolved host name af1ed198eaac04879a7497040a391120-cdd2b967bcd5983c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T10:38:03Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T10:12:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-249-to-network-check-target-ip-10-0-130-249 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-249.ec2.internal uid: 30ef9b60-4917-4faf-90a7-7ac163f98dd0 resourceVersion: "25909" uid: 165f7103-4636-4cb8-89c4-a465e78733c0 spec: sourcePod: network-check-source-7d88cb55d8-svlqb targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-28T10:19:03Z" message: 'network-check-target-ip-10-0-130-249: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 883.277µs message: 'network-check-target-ip-10-0-130-249: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:40:03Z" - latency: 887.159µs message: 'network-check-target-ip-10-0-130-249: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:39:03Z" - latency: 1.359049ms message: 'network-check-target-ip-10-0-130-249: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:38:03Z" - latency: 785.612µs message: 'network-check-target-ip-10-0-130-249: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:37:03Z" - latency: 848.432µs message: 'network-check-target-ip-10-0-130-249: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:36:03Z" - latency: 825.921µs message: 'network-check-target-ip-10-0-130-249: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:35:03Z" - latency: 1.27201ms message: 'network-check-target-ip-10-0-130-249: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:34:03Z" - latency: 1.009342ms message: 'network-check-target-ip-10-0-130-249: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:33:03Z" - latency: 821.117µs message: 'network-check-target-ip-10-0-130-249: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:32:03Z" - latency: 925.611µs message: 'network-check-target-ip-10-0-130-249: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:31:03Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T10:12:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-249-to-network-check-target-ip-10-0-132-110 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-249.ec2.internal uid: 30ef9b60-4917-4faf-90a7-7ac163f98dd0 resourceVersion: "25911" uid: eb129652-5c7f-47c1-801e-2978676c2842 spec: sourcePod: network-check-source-7d88cb55d8-svlqb targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-28T10:19:03Z" message: 'network-check-target-ip-10-0-132-110: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.158091ms message: 'network-check-target-ip-10-0-132-110: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:40:03Z" - latency: 2.032251ms message: 'network-check-target-ip-10-0-132-110: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:39:03Z" - latency: 2.101457ms message: 'network-check-target-ip-10-0-132-110: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:38:03Z" - latency: 2.160252ms message: 'network-check-target-ip-10-0-132-110: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:37:03Z" - latency: 2.395255ms message: 'network-check-target-ip-10-0-132-110: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:36:03Z" - latency: 2.621017ms message: 'network-check-target-ip-10-0-132-110: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:35:03Z" - latency: 2.330003ms message: 'network-check-target-ip-10-0-132-110: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:34:03Z" - latency: 2.138101ms message: 'network-check-target-ip-10-0-132-110: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:33:03Z" - latency: 2.035704ms message: 'network-check-target-ip-10-0-132-110: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:32:03Z" - latency: 2.152589ms message: 'network-check-target-ip-10-0-132-110: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:31:03Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T10:12:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-249-to-network-check-target-ip-10-0-135-126 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-249.ec2.internal uid: 30ef9b60-4917-4faf-90a7-7ac163f98dd0 resourceVersion: "25910" uid: 027f154a-2c4c-4911-904e-2500a595cb09 spec: sourcePod: network-check-source-7d88cb55d8-svlqb targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-28T10:19:03Z" message: 'network-check-target-ip-10-0-135-126: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.315251ms message: 'network-check-target-ip-10-0-135-126: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:40:03Z" - latency: 2.156663ms message: 'network-check-target-ip-10-0-135-126: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:39:03Z" - latency: 2.295114ms message: 'network-check-target-ip-10-0-135-126: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:38:03Z" - latency: 1.867855ms message: 'network-check-target-ip-10-0-135-126: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:37:03Z" - latency: 2.367755ms message: 'network-check-target-ip-10-0-135-126: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:36:03Z" - latency: 2.707842ms message: 'network-check-target-ip-10-0-135-126: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:35:03Z" - latency: 2.264635ms message: 'network-check-target-ip-10-0-135-126: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:34:03Z" - latency: 2.300739ms message: 'network-check-target-ip-10-0-135-126: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:33:03Z" - latency: 3.059265ms message: 'network-check-target-ip-10-0-135-126: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:32:03Z" - latency: 2.136409ms message: 'network-check-target-ip-10-0-135-126: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:31:03Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T10:12:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-249-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-249.ec2.internal uid: 30ef9b60-4917-4faf-90a7-7ac163f98dd0 resourceVersion: "27015" uid: a7c7352e-5713-44d5-aed9-fb22ce3520ec spec: sourcePod: network-check-source-7d88cb55d8-svlqb targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-28T10:18:03Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 739.388µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:42:03Z" - latency: 1.586654ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T10:42:03Z" - latency: 1.298465ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:41:03Z" - latency: 1.481684ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T10:41:03Z" - latency: 1.367512ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:40:03Z" - latency: 1.657055ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T10:40:03Z" - latency: 1.208096ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:39:03Z" - latency: 1.715693ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T10:39:03Z" - latency: 768.443µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T10:38:03Z" - latency: 1.691502ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T10:38:03Z" kind: List metadata: resourceVersion: ""