apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T23:16:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-101-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-101.ec2.internal uid: d4b7cb9d-8927-4053-b356-1851199901dd resourceVersion: "57936" uid: 05981a79-dca3-4c28-a015-a796e1abb505 spec: sourcePod: network-check-source-7d88cb55d8-x8khs targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-23T23:23:10Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 910.946µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T23:51:10Z" - latency: 1.139136ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T23:50:10Z" - latency: 905.639µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T23:49:10Z" - latency: 1.311393ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T23:48:10Z" - latency: 1.593011ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T23:47:10Z" - latency: 1.138594ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T23:46:10Z" - latency: 1.171444ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T23:45:10Z" - latency: 1.023794ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T23:44:10Z" - latency: 1.305741ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T23:43:10Z" - latency: 1.952452ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T23:42:10Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T23:16:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-101-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-101.ec2.internal uid: d4b7cb9d-8927-4053-b356-1851199901dd resourceVersion: "59041" uid: ea513673-5872-4e74-aff5-bab875ac1880 spec: sourcePod: network-check-source-7d88cb55d8-x8khs targetEndpoint: a5939c2d1b4eb4197a57325dddff4a38-ddc9f54e4a3633bb.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-23T23:22:10Z" message: 'load-balancer-api-external: tcp connection to a5939c2d1b4eb4197a57325dddff4a38-ddc9f54e4a3633bb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.711298ms message: 'load-balancer-api-external: tcp connection to a5939c2d1b4eb4197a57325dddff4a38-ddc9f54e4a3633bb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T23:52:10Z" - latency: 8.430531ms message: 'load-balancer-api-external: resolved host name a5939c2d1b4eb4197a57325dddff4a38-ddc9f54e4a3633bb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T23:52:10Z" - latency: 4.806274ms message: 'load-balancer-api-external: tcp connection to a5939c2d1b4eb4197a57325dddff4a38-ddc9f54e4a3633bb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T23:51:10Z" - latency: 9.395391ms message: 'load-balancer-api-external: resolved host name a5939c2d1b4eb4197a57325dddff4a38-ddc9f54e4a3633bb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T23:51:10Z" - latency: 4.11877ms message: 'load-balancer-api-external: tcp connection to a5939c2d1b4eb4197a57325dddff4a38-ddc9f54e4a3633bb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T23:50:10Z" - latency: 8.159329ms message: 'load-balancer-api-external: resolved host name a5939c2d1b4eb4197a57325dddff4a38-ddc9f54e4a3633bb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T23:50:10Z" - latency: 3.354016ms message: 'load-balancer-api-external: tcp connection to a5939c2d1b4eb4197a57325dddff4a38-ddc9f54e4a3633bb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T23:49:10Z" - latency: 9.089544ms message: 'load-balancer-api-external: resolved host name a5939c2d1b4eb4197a57325dddff4a38-ddc9f54e4a3633bb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T23:49:10Z" - latency: 4.979396ms message: 'load-balancer-api-external: tcp connection to a5939c2d1b4eb4197a57325dddff4a38-ddc9f54e4a3633bb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T23:48:10Z" - latency: 8.536695ms message: 'load-balancer-api-external: resolved host name a5939c2d1b4eb4197a57325dddff4a38-ddc9f54e4a3633bb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T23:48:10Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T23:16:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-101-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-101.ec2.internal uid: d4b7cb9d-8927-4053-b356-1851199901dd resourceVersion: "59042" uid: 03b24328-ae9f-4313-8439-aebda1564003 spec: sourcePod: network-check-source-7d88cb55d8-x8khs targetEndpoint: a5939c2d1b4eb4197a57325dddff4a38-ddc9f54e4a3633bb.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-23T23:22:10Z" message: 'load-balancer-api-internal: tcp connection to a5939c2d1b4eb4197a57325dddff4a38-ddc9f54e4a3633bb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.75852ms message: 'load-balancer-api-internal: tcp connection to a5939c2d1b4eb4197a57325dddff4a38-ddc9f54e4a3633bb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T23:52:10Z" - latency: 8.475559ms message: 'load-balancer-api-internal: resolved host name a5939c2d1b4eb4197a57325dddff4a38-ddc9f54e4a3633bb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T23:52:10Z" - latency: 4.796139ms message: 'load-balancer-api-internal: tcp connection to a5939c2d1b4eb4197a57325dddff4a38-ddc9f54e4a3633bb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T23:51:10Z" - latency: 9.367032ms message: 'load-balancer-api-internal: resolved host name a5939c2d1b4eb4197a57325dddff4a38-ddc9f54e4a3633bb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T23:51:10Z" - latency: 4.093878ms message: 'load-balancer-api-internal: tcp connection to a5939c2d1b4eb4197a57325dddff4a38-ddc9f54e4a3633bb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T23:50:10Z" - latency: 8.2068ms message: 'load-balancer-api-internal: resolved host name a5939c2d1b4eb4197a57325dddff4a38-ddc9f54e4a3633bb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T23:50:10Z" - latency: 3.135181ms message: 'load-balancer-api-internal: tcp connection to a5939c2d1b4eb4197a57325dddff4a38-ddc9f54e4a3633bb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T23:49:10Z" - latency: 9.027578ms message: 'load-balancer-api-internal: resolved host name a5939c2d1b4eb4197a57325dddff4a38-ddc9f54e4a3633bb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T23:49:10Z" - latency: 4.095768ms message: 'load-balancer-api-internal: tcp connection to a5939c2d1b4eb4197a57325dddff4a38-ddc9f54e4a3633bb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T23:48:10Z" - latency: 8.45964ms message: 'load-balancer-api-internal: resolved host name a5939c2d1b4eb4197a57325dddff4a38-ddc9f54e4a3633bb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T23:48:10Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T23:16:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-101-to-network-check-target-ip-10-0-129-165 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-101.ec2.internal uid: d4b7cb9d-8927-4053-b356-1851199901dd resourceVersion: "57934" uid: cb261213-aa85-41af-8eb7-99fe35b86a2f spec: sourcePod: network-check-source-7d88cb55d8-x8khs targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-23T23:23:10Z" message: 'network-check-target-ip-10-0-129-165: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.872373ms message: 'network-check-target-ip-10-0-129-165: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T23:51:10Z" - latency: 1.977209ms message: 'network-check-target-ip-10-0-129-165: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T23:50:10Z" - latency: 2.488906ms message: 'network-check-target-ip-10-0-129-165: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T23:49:10Z" - latency: 2.507458ms message: 'network-check-target-ip-10-0-129-165: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T23:48:10Z" - latency: 2.544927ms message: 'network-check-target-ip-10-0-129-165: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T23:47:10Z" - latency: 2.067954ms message: 'network-check-target-ip-10-0-129-165: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T23:46:10Z" - latency: 2.854499ms message: 'network-check-target-ip-10-0-129-165: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T23:45:10Z" - latency: 2.274116ms message: 'network-check-target-ip-10-0-129-165: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T23:44:10Z" - latency: 2.079564ms message: 'network-check-target-ip-10-0-129-165: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T23:43:10Z" - latency: 2.372237ms message: 'network-check-target-ip-10-0-129-165: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T23:42:10Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T23:16:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-101-to-network-check-target-ip-10-0-129-178 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-101.ec2.internal uid: d4b7cb9d-8927-4053-b356-1851199901dd resourceVersion: "57935" uid: 5415cdbd-d2d6-41bd-b576-6463ff0cc2dd spec: sourcePod: network-check-source-7d88cb55d8-x8khs targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-23T23:23:10Z" message: 'network-check-target-ip-10-0-129-178: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.287033ms message: 'network-check-target-ip-10-0-129-178: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T23:51:10Z" - latency: 2.329575ms message: 'network-check-target-ip-10-0-129-178: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T23:50:10Z" - latency: 2.576271ms message: 'network-check-target-ip-10-0-129-178: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T23:49:10Z" - latency: 3.239955ms message: 'network-check-target-ip-10-0-129-178: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T23:48:10Z" - latency: 2.675287ms message: 'network-check-target-ip-10-0-129-178: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T23:47:10Z" - latency: 2.354559ms message: 'network-check-target-ip-10-0-129-178: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T23:46:10Z" - latency: 2.695274ms message: 'network-check-target-ip-10-0-129-178: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T23:45:10Z" - latency: 2.31546ms message: 'network-check-target-ip-10-0-129-178: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T23:44:10Z" - latency: 2.317222ms message: 'network-check-target-ip-10-0-129-178: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T23:43:10Z" - latency: 2.437892ms message: 'network-check-target-ip-10-0-129-178: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T23:42:10Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T23:16:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-101-to-network-check-target-ip-10-0-135-101 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-101.ec2.internal uid: d4b7cb9d-8927-4053-b356-1851199901dd resourceVersion: "57933" uid: 43db1a2a-1cfb-490f-86d7-308372c3b8e7 spec: sourcePod: network-check-source-7d88cb55d8-x8khs targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-23T23:23:10Z" message: 'network-check-target-ip-10-0-135-101: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.133892ms message: 'network-check-target-ip-10-0-135-101: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T23:51:10Z" - latency: 822.823µs message: 'network-check-target-ip-10-0-135-101: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T23:50:10Z" - latency: 861.936µs message: 'network-check-target-ip-10-0-135-101: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T23:49:10Z" - latency: 842.009µs message: 'network-check-target-ip-10-0-135-101: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T23:48:10Z" - latency: 1.8039ms message: 'network-check-target-ip-10-0-135-101: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T23:47:10Z" - latency: 861.522µs message: 'network-check-target-ip-10-0-135-101: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T23:46:10Z" - latency: 779.653µs message: 'network-check-target-ip-10-0-135-101: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T23:45:10Z" - latency: 1.104161ms message: 'network-check-target-ip-10-0-135-101: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T23:44:10Z" - latency: 727.578µs message: 'network-check-target-ip-10-0-135-101: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T23:43:10Z" - latency: 1.490901ms message: 'network-check-target-ip-10-0-135-101: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T23:42:10Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T23:16:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-101-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-101.ec2.internal uid: d4b7cb9d-8927-4053-b356-1851199901dd resourceVersion: "59040" uid: 17015878-408d-43ae-a7aa-9d97d73c8fac spec: sourcePod: network-check-source-7d88cb55d8-x8khs targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-23T23:22:10Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 881.909µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-23T23:52:10Z" - latency: 1.87831ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-23T23:52:10Z" - latency: 1.060989ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-23T23:51:10Z" - latency: 1.930937ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-23T23:51:10Z" - latency: 856.926µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-23T23:50:10Z" - latency: 1.571064ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-23T23:50:10Z" - latency: 894.238µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-23T23:49:10Z" - latency: 1.822874ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-23T23:49:10Z" - latency: 1.221769ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-23T23:48:10Z" - latency: 2.038364ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-23T23:48:10Z" kind: List metadata: resourceVersion: ""