apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T01:15:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-179-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-179.us-west-2.compute.internal uid: bcd8bb9c-5fa3-4e0a-9811-04ccdf255672 resourceVersion: "57183" uid: d84d6b8f-6079-4511-99a9-1b87514088cd spec: sourcePod: network-check-source-6f78d59f99-dbnq4 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-11-04T01:22:21Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.118208ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:50:20Z" - latency: 1.162268ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:49:20Z" - latency: 1.913011ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:48:20Z" - latency: 1.087427ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:47:20Z" - latency: 1.057137ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:46:20Z" - latency: 1.380828ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:45:20Z" - latency: 987.079µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:44:20Z" - latency: 932.627µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:43:20Z" - latency: 1.028968ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:42:20Z" - latency: 1.088227ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:41:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T01:15:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-179-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-179.us-west-2.compute.internal uid: bcd8bb9c-5fa3-4e0a-9811-04ccdf255672 resourceVersion: "52153" uid: f49a0d21-67e4-4f5f-89c4-eea9e557e3c5 spec: sourcePod: network-check-source-6f78d59f99-dbnq4 targetEndpoint: a3e660436c5ac4b748d5d3f99dae8da8-e741eb2aa4dd6e95.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-04T01:21:21Z" message: 'load-balancer-api-external: tcp connection to a3e660436c5ac4b748d5d3f99dae8da8-e741eb2aa4dd6e95.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 56.808134ms message: 'load-balancer-api-external: tcp connection to a3e660436c5ac4b748d5d3f99dae8da8-e741eb2aa4dd6e95.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:45:20Z" - latency: 6.895796ms message: 'load-balancer-api-external: resolved host name a3e660436c5ac4b748d5d3f99dae8da8-e741eb2aa4dd6e95.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T01:45:20Z" - latency: 57.897174ms message: 'load-balancer-api-external: tcp connection to a3e660436c5ac4b748d5d3f99dae8da8-e741eb2aa4dd6e95.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:44:20Z" - latency: 8.325428ms message: 'load-balancer-api-external: resolved host name a3e660436c5ac4b748d5d3f99dae8da8-e741eb2aa4dd6e95.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T01:44:20Z" - latency: 53.949186ms message: 'load-balancer-api-external: tcp connection to a3e660436c5ac4b748d5d3f99dae8da8-e741eb2aa4dd6e95.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:43:20Z" - latency: 6.914727ms message: 'load-balancer-api-external: resolved host name a3e660436c5ac4b748d5d3f99dae8da8-e741eb2aa4dd6e95.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T01:43:20Z" - latency: 54.520819ms message: 'load-balancer-api-external: tcp connection to a3e660436c5ac4b748d5d3f99dae8da8-e741eb2aa4dd6e95.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:42:20Z" - latency: 6.849051ms message: 'load-balancer-api-external: resolved host name a3e660436c5ac4b748d5d3f99dae8da8-e741eb2aa4dd6e95.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T01:42:20Z" - latency: 50.219631ms message: 'load-balancer-api-external: tcp connection to a3e660436c5ac4b748d5d3f99dae8da8-e741eb2aa4dd6e95.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:41:20Z" - latency: 7.135128ms message: 'load-balancer-api-external: resolved host name a3e660436c5ac4b748d5d3f99dae8da8-e741eb2aa4dd6e95.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T01:41:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T01:15:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-179-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-179.us-west-2.compute.internal uid: bcd8bb9c-5fa3-4e0a-9811-04ccdf255672 resourceVersion: "52154" uid: 9b42409d-a184-441f-9f64-1b34f7e467a3 spec: sourcePod: network-check-source-6f78d59f99-dbnq4 targetEndpoint: a3e660436c5ac4b748d5d3f99dae8da8-e741eb2aa4dd6e95.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-04T01:21:21Z" message: 'load-balancer-api-internal: tcp connection to a3e660436c5ac4b748d5d3f99dae8da8-e741eb2aa4dd6e95.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 56.910872ms message: 'load-balancer-api-internal: tcp connection to a3e660436c5ac4b748d5d3f99dae8da8-e741eb2aa4dd6e95.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:45:20Z" - latency: 6.828178ms message: 'load-balancer-api-internal: resolved host name a3e660436c5ac4b748d5d3f99dae8da8-e741eb2aa4dd6e95.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T01:45:20Z" - latency: 57.891626ms message: 'load-balancer-api-internal: tcp connection to a3e660436c5ac4b748d5d3f99dae8da8-e741eb2aa4dd6e95.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:44:20Z" - latency: 8.27082ms message: 'load-balancer-api-internal: resolved host name a3e660436c5ac4b748d5d3f99dae8da8-e741eb2aa4dd6e95.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T01:44:20Z" - latency: 50.899841ms message: 'load-balancer-api-internal: tcp connection to a3e660436c5ac4b748d5d3f99dae8da8-e741eb2aa4dd6e95.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:43:20Z" - latency: 6.819366ms message: 'load-balancer-api-internal: resolved host name a3e660436c5ac4b748d5d3f99dae8da8-e741eb2aa4dd6e95.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T01:43:20Z" - latency: 54.514171ms message: 'load-balancer-api-internal: tcp connection to a3e660436c5ac4b748d5d3f99dae8da8-e741eb2aa4dd6e95.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:42:20Z" - latency: 6.910091ms message: 'load-balancer-api-internal: resolved host name a3e660436c5ac4b748d5d3f99dae8da8-e741eb2aa4dd6e95.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T01:42:20Z" - latency: 52.497581ms message: 'load-balancer-api-internal: tcp connection to a3e660436c5ac4b748d5d3f99dae8da8-e741eb2aa4dd6e95.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:41:20Z" - latency: 7.007043ms message: 'load-balancer-api-internal: resolved host name a3e660436c5ac4b748d5d3f99dae8da8-e741eb2aa4dd6e95.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T01:41:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T01:15:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-179-to-network-check-target-ip-10-0-128-142 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-179.us-west-2.compute.internal uid: bcd8bb9c-5fa3-4e0a-9811-04ccdf255672 resourceVersion: "57182" uid: bbb69311-8737-435f-aa50-83c5e46b757e spec: sourcePod: network-check-source-6f78d59f99-dbnq4 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-11-04T01:22:20Z" message: 'network-check-target-ip-10-0-128-142: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.632127ms message: 'network-check-target-ip-10-0-128-142: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:50:20Z" - latency: 2.754611ms message: 'network-check-target-ip-10-0-128-142: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:49:20Z" - latency: 2.538285ms message: 'network-check-target-ip-10-0-128-142: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:48:20Z" - latency: 2.569241ms message: 'network-check-target-ip-10-0-128-142: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:47:20Z" - latency: 2.362433ms message: 'network-check-target-ip-10-0-128-142: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:46:20Z" - latency: 2.70378ms message: 'network-check-target-ip-10-0-128-142: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:45:20Z" - latency: 2.559177ms message: 'network-check-target-ip-10-0-128-142: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:44:20Z" - latency: 2.675461ms message: 'network-check-target-ip-10-0-128-142: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:43:20Z" - latency: 2.384524ms message: 'network-check-target-ip-10-0-128-142: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:42:20Z" - latency: 2.401257ms message: 'network-check-target-ip-10-0-128-142: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:41:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T01:15:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-179-to-network-check-target-ip-10-0-131-51 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-179.us-west-2.compute.internal uid: bcd8bb9c-5fa3-4e0a-9811-04ccdf255672 resourceVersion: "57181" uid: c84e7bd5-548d-4225-b3d9-e91c04b7cce8 spec: sourcePod: network-check-source-6f78d59f99-dbnq4 targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-11-04T01:22:20Z" message: 'network-check-target-ip-10-0-131-51: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.499409ms message: 'network-check-target-ip-10-0-131-51: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:50:20Z" - latency: 2.308243ms message: 'network-check-target-ip-10-0-131-51: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:49:20Z" - latency: 3.478848ms message: 'network-check-target-ip-10-0-131-51: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:48:20Z" - latency: 2.77062ms message: 'network-check-target-ip-10-0-131-51: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:47:20Z" - latency: 2.50706ms message: 'network-check-target-ip-10-0-131-51: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:46:20Z" - latency: 2.71628ms message: 'network-check-target-ip-10-0-131-51: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:45:20Z" - latency: 3.166973ms message: 'network-check-target-ip-10-0-131-51: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:44:20Z" - latency: 2.596427ms message: 'network-check-target-ip-10-0-131-51: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:43:20Z" - latency: 2.362744ms message: 'network-check-target-ip-10-0-131-51: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:42:20Z" - latency: 2.869475ms message: 'network-check-target-ip-10-0-131-51: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:41:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T01:15:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-179-to-network-check-target-ip-10-0-138-179 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-179.us-west-2.compute.internal uid: bcd8bb9c-5fa3-4e0a-9811-04ccdf255672 resourceVersion: "57180" uid: d8c65759-1e77-4e4f-9f6d-009722bac9cf spec: sourcePod: network-check-source-6f78d59f99-dbnq4 targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-11-04T01:22:20Z" message: 'network-check-target-ip-10-0-138-179: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.025675ms message: 'network-check-target-ip-10-0-138-179: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:50:20Z" - latency: 1.66286ms message: 'network-check-target-ip-10-0-138-179: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:49:20Z" - latency: 1.756777ms message: 'network-check-target-ip-10-0-138-179: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:48:20Z" - latency: 1.643527ms message: 'network-check-target-ip-10-0-138-179: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:47:20Z" - latency: 926.838µs message: 'network-check-target-ip-10-0-138-179: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:46:20Z" - latency: 1.348029ms message: 'network-check-target-ip-10-0-138-179: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:45:20Z" - latency: 1.033624ms message: 'network-check-target-ip-10-0-138-179: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:44:20Z" - latency: 980.092µs message: 'network-check-target-ip-10-0-138-179: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:43:20Z" - latency: 1.011947ms message: 'network-check-target-ip-10-0-138-179: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:42:20Z" - latency: 970.737µs message: 'network-check-target-ip-10-0-138-179: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:41:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T01:15:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-179-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-179.us-west-2.compute.internal uid: bcd8bb9c-5fa3-4e0a-9811-04ccdf255672 resourceVersion: "52150" uid: aaef9ef6-6d97-4f5f-b5d3-efc2bfac1fee spec: sourcePod: network-check-source-6f78d59f99-dbnq4 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-11-04T01:21:20Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.262375ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:45:20Z" - latency: 2.045642ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-04T01:45:20Z" - latency: 916.567µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:44:20Z" - latency: 2.557415ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-04T01:44:20Z" - latency: 1.259302ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:43:20Z" - latency: 2.240701ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-04T01:43:20Z" - latency: 978.351µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:42:20Z" - latency: 1.835287ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-04T01:42:20Z" - latency: 1.165344ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:41:20Z" - latency: 1.835924ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-04T01:41:20Z" kind: List metadata: resourceVersion: ""