apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T16:53:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-180-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-180.ec2.internal
      uid: 7eb5142b-2ae8-48d6-b550-439482e38b18
    resourceVersion: "14275"
    uid: 520321f0-d8dd-4a96-ab35-14daaae373c5
  spec:
    sourcePod: network-check-source-7d88cb55d8-x8t9w
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T17:00:59Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 952.155µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:00:59Z"
    - latency: 872.616µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T16:59:59Z"
    - latency: 939.665µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T16:58:59Z"
    - latency: 848.52µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T16:57:59Z"
    - latency: 1.203959ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T16:56:59Z"
    - latency: 1.11993ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T16:55:59Z"
    - latency: 1.279029ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T16:54:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T16:53:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-180-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-180.ec2.internal
      uid: 7eb5142b-2ae8-48d6-b550-439482e38b18
    resourceVersion: "16015"
    uid: 8e456e83-f93f-4423-9007-82164dc1ebe1
  spec:
    sourcePod: network-check-source-7d88cb55d8-x8t9w
    targetEndpoint: a6e68c1365bfb4955adc974933b781f1-b7bbc532d20b396c.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T16:59:59Z"
      message: 'load-balancer-api-external: tcp connection to a6e68c1365bfb4955adc974933b781f1-b7bbc532d20b396c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.961478ms
      message: 'load-balancer-api-external: tcp connection to a6e68c1365bfb4955adc974933b781f1-b7bbc532d20b396c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:05:59Z"
    - latency: 6.834572ms
      message: 'load-balancer-api-external: resolved host name a6e68c1365bfb4955adc974933b781f1-b7bbc532d20b396c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T17:05:59Z"
    - latency: 5.460623ms
      message: 'load-balancer-api-external: tcp connection to a6e68c1365bfb4955adc974933b781f1-b7bbc532d20b396c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:04:59Z"
    - latency: 7.949118ms
      message: 'load-balancer-api-external: resolved host name a6e68c1365bfb4955adc974933b781f1-b7bbc532d20b396c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T17:04:59Z"
    - latency: 4.191047ms
      message: 'load-balancer-api-external: tcp connection to a6e68c1365bfb4955adc974933b781f1-b7bbc532d20b396c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:03:59Z"
    - latency: 9.155692ms
      message: 'load-balancer-api-external: resolved host name a6e68c1365bfb4955adc974933b781f1-b7bbc532d20b396c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T17:03:59Z"
    - latency: 4.725408ms
      message: 'load-balancer-api-external: tcp connection to a6e68c1365bfb4955adc974933b781f1-b7bbc532d20b396c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:02:59Z"
    - latency: 6.582474ms
      message: 'load-balancer-api-external: resolved host name a6e68c1365bfb4955adc974933b781f1-b7bbc532d20b396c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T17:02:59Z"
    - latency: 4.624005ms
      message: 'load-balancer-api-external: tcp connection to a6e68c1365bfb4955adc974933b781f1-b7bbc532d20b396c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:01:59Z"
    - latency: 8.044121ms
      message: 'load-balancer-api-external: resolved host name a6e68c1365bfb4955adc974933b781f1-b7bbc532d20b396c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T17:01:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T16:53:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-180-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-180.ec2.internal
      uid: 7eb5142b-2ae8-48d6-b550-439482e38b18
    resourceVersion: "16016"
    uid: 92dd648c-25ea-4ece-9d67-13a8241ca8c3
  spec:
    sourcePod: network-check-source-7d88cb55d8-x8t9w
    targetEndpoint: a6e68c1365bfb4955adc974933b781f1-b7bbc532d20b396c.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T16:59:59Z"
      message: 'load-balancer-api-internal: tcp connection to a6e68c1365bfb4955adc974933b781f1-b7bbc532d20b396c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.20168ms
      message: 'load-balancer-api-internal: tcp connection to a6e68c1365bfb4955adc974933b781f1-b7bbc532d20b396c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:05:59Z"
    - latency: 6.899568ms
      message: 'load-balancer-api-internal: resolved host name a6e68c1365bfb4955adc974933b781f1-b7bbc532d20b396c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T17:05:59Z"
    - latency: 5.477904ms
      message: 'load-balancer-api-internal: tcp connection to a6e68c1365bfb4955adc974933b781f1-b7bbc532d20b396c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:04:59Z"
    - latency: 8.041711ms
      message: 'load-balancer-api-internal: resolved host name a6e68c1365bfb4955adc974933b781f1-b7bbc532d20b396c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T17:04:59Z"
    - latency: 4.88025ms
      message: 'load-balancer-api-internal: tcp connection to a6e68c1365bfb4955adc974933b781f1-b7bbc532d20b396c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:03:59Z"
    - latency: 9.20636ms
      message: 'load-balancer-api-internal: resolved host name a6e68c1365bfb4955adc974933b781f1-b7bbc532d20b396c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T17:03:59Z"
    - latency: 4.701588ms
      message: 'load-balancer-api-internal: tcp connection to a6e68c1365bfb4955adc974933b781f1-b7bbc532d20b396c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:02:59Z"
    - latency: 6.626165ms
      message: 'load-balancer-api-internal: resolved host name a6e68c1365bfb4955adc974933b781f1-b7bbc532d20b396c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T17:02:59Z"
    - latency: 4.64635ms
      message: 'load-balancer-api-internal: tcp connection to a6e68c1365bfb4955adc974933b781f1-b7bbc532d20b396c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:01:59Z"
    - latency: 8.085828ms
      message: 'load-balancer-api-internal: resolved host name a6e68c1365bfb4955adc974933b781f1-b7bbc532d20b396c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T17:01:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T16:53:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-180-to-network-check-target-ip-10-0-138-214
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-180.ec2.internal
      uid: 7eb5142b-2ae8-48d6-b550-439482e38b18
    resourceVersion: "14274"
    uid: 95c7b049-6892-4b41-9666-320a95ac3b1c
  spec:
    sourcePod: network-check-source-7d88cb55d8-x8t9w
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T17:00:59Z"
      message: 'network-check-target-ip-10-0-138-214: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.372232ms
      message: 'network-check-target-ip-10-0-138-214: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:00:59Z"
    - latency: 1.943524ms
      message: 'network-check-target-ip-10-0-138-214: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T16:59:59Z"
    - latency: 2.165178ms
      message: 'network-check-target-ip-10-0-138-214: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T16:58:59Z"
    - latency: 2.436069ms
      message: 'network-check-target-ip-10-0-138-214: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T16:57:59Z"
    - latency: 1.978898ms
      message: 'network-check-target-ip-10-0-138-214: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T16:56:59Z"
    - latency: 2.045543ms
      message: 'network-check-target-ip-10-0-138-214: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T16:55:59Z"
    - latency: 2.616887ms
      message: 'network-check-target-ip-10-0-138-214: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T16:54:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T16:53:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-180-to-network-check-target-ip-10-0-140-180
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-180.ec2.internal
      uid: 7eb5142b-2ae8-48d6-b550-439482e38b18
    resourceVersion: "14272"
    uid: 68e6bfde-4837-4d63-a3b7-6b898dae52e5
  spec:
    sourcePod: network-check-source-7d88cb55d8-x8t9w
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T17:00:59Z"
      message: 'network-check-target-ip-10-0-140-180: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.449204ms
      message: 'network-check-target-ip-10-0-140-180: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:00:59Z"
    - latency: 965.767µs
      message: 'network-check-target-ip-10-0-140-180: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T16:59:59Z"
    - latency: 866.296µs
      message: 'network-check-target-ip-10-0-140-180: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T16:58:59Z"
    - latency: 1.405908ms
      message: 'network-check-target-ip-10-0-140-180: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T16:57:59Z"
    - latency: 897.44µs
      message: 'network-check-target-ip-10-0-140-180: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T16:56:59Z"
    - latency: 1.40143ms
      message: 'network-check-target-ip-10-0-140-180: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T16:55:59Z"
    - latency: 1.906875ms
      message: 'network-check-target-ip-10-0-140-180: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T16:54:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T16:53:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-180-to-network-check-target-ip-10-0-142-232
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-180.ec2.internal
      uid: 7eb5142b-2ae8-48d6-b550-439482e38b18
    resourceVersion: "14273"
    uid: d405d518-c548-4544-8196-cfc21849be17
  spec:
    sourcePod: network-check-source-7d88cb55d8-x8t9w
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T17:00:59Z"
      message: 'network-check-target-ip-10-0-142-232: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.454564ms
      message: 'network-check-target-ip-10-0-142-232: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:00:59Z"
    - latency: 2.687509ms
      message: 'network-check-target-ip-10-0-142-232: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T16:59:59Z"
    - latency: 2.396783ms
      message: 'network-check-target-ip-10-0-142-232: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T16:58:59Z"
    - latency: 2.428425ms
      message: 'network-check-target-ip-10-0-142-232: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T16:57:59Z"
    - latency: 2.394598ms
      message: 'network-check-target-ip-10-0-142-232: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T16:56:59Z"
    - latency: 2.376163ms
      message: 'network-check-target-ip-10-0-142-232: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T16:55:59Z"
    - latency: 2.274859ms
      message: 'network-check-target-ip-10-0-142-232: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T16:54:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T16:53:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-180-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-180.ec2.internal
      uid: 7eb5142b-2ae8-48d6-b550-439482e38b18
    resourceVersion: "16014"
    uid: 535c67f1-d792-4b42-9185-cd9e0a84a9fd
  spec:
    sourcePod: network-check-source-7d88cb55d8-x8t9w
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T16:59:59Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 892.397µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:05:59Z"
    - latency: 1.831307ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T17:05:59Z"
    - latency: 805.485µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:04:59Z"
    - latency: 1.699804ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T17:04:59Z"
    - latency: 989.953µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:03:59Z"
    - latency: 1.747215ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T17:03:59Z"
    - latency: 991.988µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:02:59Z"
    - latency: 1.768726ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T17:02:59Z"
    - latency: 783.035µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:01:59Z"
    - latency: 1.730503ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T17:01:59Z"
kind: List
metadata:
  resourceVersion: ""