apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T21:52:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-173-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-173.ec2.internal uid: 74b88cb8-0331-4fd0-ab65-1478e004b447 resourceVersion: "68338" uid: 6a9b7a03-f118-446e-84ca-676dc30bbbe4 spec: sourcePod: network-check-source-7bc5b6bf85-pwrkk targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-16T21:59:08Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.10961ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:41:08Z" - latency: 1.381828ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:40:08Z" - latency: 931.337µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:39:08Z" - latency: 877.328µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:38:08Z" - latency: 910.338µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:37:08Z" - latency: 1.853677ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:36:08Z" - latency: 1.22537ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:35:08Z" - latency: 1.331378ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:34:08Z" - latency: 1.317243ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:33:08Z" - latency: 865.639µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:32:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T21:52:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-173-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-173.ec2.internal uid: 74b88cb8-0331-4fd0-ab65-1478e004b447 resourceVersion: "74088" uid: 08f51f05-2ca7-4a62-961b-60981e76007b spec: sourcePod: network-check-source-7bc5b6bf85-pwrkk targetEndpoint: a2fdc2f86f8f24f08ac3b8fd79d59d71-72cb86faf085b4e7.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-16T21:58:08Z" message: 'load-balancer-api-external: tcp connection to a2fdc2f86f8f24f08ac3b8fd79d59d71-72cb86faf085b4e7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.196241ms message: 'load-balancer-api-external: tcp connection to a2fdc2f86f8f24f08ac3b8fd79d59d71-72cb86faf085b4e7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:46:08Z" - latency: 11.689389ms message: 'load-balancer-api-external: resolved host name a2fdc2f86f8f24f08ac3b8fd79d59d71-72cb86faf085b4e7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T22:46:08Z" - latency: 4.55181ms message: 'load-balancer-api-external: tcp connection to a2fdc2f86f8f24f08ac3b8fd79d59d71-72cb86faf085b4e7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:45:08Z" - latency: 8.31922ms message: 'load-balancer-api-external: resolved host name a2fdc2f86f8f24f08ac3b8fd79d59d71-72cb86faf085b4e7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T22:45:08Z" - latency: 5.020015ms message: 'load-balancer-api-external: tcp connection to a2fdc2f86f8f24f08ac3b8fd79d59d71-72cb86faf085b4e7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:44:08Z" - latency: 7.090393ms message: 'load-balancer-api-external: resolved host name a2fdc2f86f8f24f08ac3b8fd79d59d71-72cb86faf085b4e7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T22:44:08Z" - latency: 4.282805ms message: 'load-balancer-api-external: tcp connection to a2fdc2f86f8f24f08ac3b8fd79d59d71-72cb86faf085b4e7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:43:08Z" - latency: 11.149006ms message: 'load-balancer-api-external: resolved host name a2fdc2f86f8f24f08ac3b8fd79d59d71-72cb86faf085b4e7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T22:43:08Z" - latency: 3.751815ms message: 'load-balancer-api-external: tcp connection to a2fdc2f86f8f24f08ac3b8fd79d59d71-72cb86faf085b4e7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:42:08Z" - latency: 7.05278ms message: 'load-balancer-api-external: resolved host name a2fdc2f86f8f24f08ac3b8fd79d59d71-72cb86faf085b4e7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T22:42:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T21:52:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-173-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-173.ec2.internal uid: 74b88cb8-0331-4fd0-ab65-1478e004b447 resourceVersion: "74087" uid: 12bec473-7aa8-4e77-b2eb-566c0b493452 spec: sourcePod: network-check-source-7bc5b6bf85-pwrkk targetEndpoint: a2fdc2f86f8f24f08ac3b8fd79d59d71-72cb86faf085b4e7.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-16T21:58:08Z" message: 'load-balancer-api-internal: tcp connection to a2fdc2f86f8f24f08ac3b8fd79d59d71-72cb86faf085b4e7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.497236ms message: 'load-balancer-api-internal: tcp connection to a2fdc2f86f8f24f08ac3b8fd79d59d71-72cb86faf085b4e7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:46:08Z" - latency: 11.663965ms message: 'load-balancer-api-internal: resolved host name a2fdc2f86f8f24f08ac3b8fd79d59d71-72cb86faf085b4e7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T22:46:08Z" - latency: 6.316151ms message: 'load-balancer-api-internal: tcp connection to a2fdc2f86f8f24f08ac3b8fd79d59d71-72cb86faf085b4e7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:45:08Z" - latency: 8.375209ms message: 'load-balancer-api-internal: resolved host name a2fdc2f86f8f24f08ac3b8fd79d59d71-72cb86faf085b4e7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T22:45:08Z" - latency: 4.136574ms message: 'load-balancer-api-internal: tcp connection to a2fdc2f86f8f24f08ac3b8fd79d59d71-72cb86faf085b4e7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:44:08Z" - latency: 7.152037ms message: 'load-balancer-api-internal: resolved host name a2fdc2f86f8f24f08ac3b8fd79d59d71-72cb86faf085b4e7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T22:44:08Z" - latency: 4.281353ms message: 'load-balancer-api-internal: tcp connection to a2fdc2f86f8f24f08ac3b8fd79d59d71-72cb86faf085b4e7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:43:08Z" - latency: 11.108921ms message: 'load-balancer-api-internal: resolved host name a2fdc2f86f8f24f08ac3b8fd79d59d71-72cb86faf085b4e7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T22:43:08Z" - latency: 6.058017ms message: 'load-balancer-api-internal: tcp connection to a2fdc2f86f8f24f08ac3b8fd79d59d71-72cb86faf085b4e7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:42:08Z" - latency: 7.081875ms message: 'load-balancer-api-internal: resolved host name a2fdc2f86f8f24f08ac3b8fd79d59d71-72cb86faf085b4e7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T22:42:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T21:52:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-173-to-network-check-target-ip-10-0-128-173 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-173.ec2.internal uid: 74b88cb8-0331-4fd0-ab65-1478e004b447 resourceVersion: "68335" uid: e124c74d-14b2-4110-a107-f0bc5bda55c6 spec: sourcePod: network-check-source-7bc5b6bf85-pwrkk targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-16T21:59:08Z" message: 'network-check-target-ip-10-0-128-173: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.336713ms message: 'network-check-target-ip-10-0-128-173: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:41:08Z" - latency: 1.425567ms message: 'network-check-target-ip-10-0-128-173: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:40:08Z" - latency: 996.054µs message: 'network-check-target-ip-10-0-128-173: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:39:08Z" - latency: 1.218486ms message: 'network-check-target-ip-10-0-128-173: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:38:08Z" - latency: 1.362348ms message: 'network-check-target-ip-10-0-128-173: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:37:08Z" - latency: 1.347337ms message: 'network-check-target-ip-10-0-128-173: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:36:08Z" - latency: 1.093035ms message: 'network-check-target-ip-10-0-128-173: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:35:08Z" - latency: 1.869878ms message: 'network-check-target-ip-10-0-128-173: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:34:08Z" - latency: 1.083522ms message: 'network-check-target-ip-10-0-128-173: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:33:08Z" - latency: 1.227465ms message: 'network-check-target-ip-10-0-128-173: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:32:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T21:52:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-173-to-network-check-target-ip-10-0-131-79 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-173.ec2.internal uid: 74b88cb8-0331-4fd0-ab65-1478e004b447 resourceVersion: "68336" uid: c49a37d8-d1ba-416a-9496-281847be8496 spec: sourcePod: network-check-source-7bc5b6bf85-pwrkk targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-16T21:59:08Z" message: 'network-check-target-ip-10-0-131-79: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.484423ms message: 'network-check-target-ip-10-0-131-79: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:41:08Z" - latency: 2.601663ms message: 'network-check-target-ip-10-0-131-79: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:40:08Z" - latency: 1.94598ms message: 'network-check-target-ip-10-0-131-79: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:39:08Z" - latency: 2.195119ms message: 'network-check-target-ip-10-0-131-79: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:38:08Z" - latency: 2.382832ms message: 'network-check-target-ip-10-0-131-79: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:37:08Z" - latency: 2.652279ms message: 'network-check-target-ip-10-0-131-79: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:36:08Z" - latency: 2.27784ms message: 'network-check-target-ip-10-0-131-79: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:35:08Z" - latency: 2.289597ms message: 'network-check-target-ip-10-0-131-79: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:34:08Z" - latency: 2.367946ms message: 'network-check-target-ip-10-0-131-79: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:33:08Z" - latency: 2.315111ms message: 'network-check-target-ip-10-0-131-79: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:32:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T21:52:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-173-to-network-check-target-ip-10-0-141-223 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-173.ec2.internal uid: 74b88cb8-0331-4fd0-ab65-1478e004b447 resourceVersion: "68337" uid: 3038c152-d36e-4d56-8f56-b775077bf45b spec: sourcePod: network-check-source-7bc5b6bf85-pwrkk targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-16T21:59:08Z" message: 'network-check-target-ip-10-0-141-223: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.490038ms message: 'network-check-target-ip-10-0-141-223: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:41:08Z" - latency: 2.202871ms message: 'network-check-target-ip-10-0-141-223: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:40:08Z" - latency: 2.126785ms message: 'network-check-target-ip-10-0-141-223: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:39:08Z" - latency: 2.205789ms message: 'network-check-target-ip-10-0-141-223: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:38:08Z" - latency: 2.13114ms message: 'network-check-target-ip-10-0-141-223: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:37:08Z" - latency: 2.670387ms message: 'network-check-target-ip-10-0-141-223: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:36:08Z" - latency: 2.225233ms message: 'network-check-target-ip-10-0-141-223: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:35:08Z" - latency: 2.724591ms message: 'network-check-target-ip-10-0-141-223: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:34:08Z" - latency: 2.313727ms message: 'network-check-target-ip-10-0-141-223: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:33:08Z" - latency: 2.41034ms message: 'network-check-target-ip-10-0-141-223: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:32:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T21:52:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-173-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-173.ec2.internal uid: 74b88cb8-0331-4fd0-ab65-1478e004b447 resourceVersion: "74086" uid: 28d602ff-06bc-4b00-bf8a-cf8babe38c92 spec: sourcePod: network-check-source-7bc5b6bf85-pwrkk targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-16T21:58:08Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.152039ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:46:08Z" - latency: 1.983251ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T22:46:08Z" - latency: 1.0986ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:45:08Z" - latency: 2.248914ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T22:45:08Z" - latency: 1.169826ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:44:08Z" - latency: 1.969615ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T22:44:08Z" - latency: 882.024µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:43:08Z" - latency: 2.527379ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T22:43:08Z" - latency: 968.469µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:42:08Z" - latency: 2.036979ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T22:42:08Z" kind: List metadata: resourceVersion: ""