apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T20:58:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-5-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-5.ec2.internal
      uid: 3279ca2d-3a78-45f0-b294-6f799c74504c
    resourceVersion: "24024"
    uid: 065d6767-6dde-4efd-925b-e56ba701c3c7
  spec:
    sourcePod: network-check-source-685456655f-bhbhz
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T21:05:27Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.400552ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:05:27Z"
    - latency: 1.242081ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:04:27Z"
    - latency: 952.838µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:03:27Z"
    - latency: 859.711µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:02:27Z"
    - latency: 1.011218ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:01:27Z"
    - latency: 1.357551ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:00:27Z"
    - latency: 1.261139ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:59:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T20:58:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-5-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-5.ec2.internal
      uid: 3279ca2d-3a78-45f0-b294-6f799c74504c
    resourceVersion: "22832"
    uid: 382bc884-cd01-4b58-ac0b-abdc27929111
  spec:
    sourcePod: network-check-source-685456655f-bhbhz
    targetEndpoint: add0864408f98408387cb0980557d9ef-4b5d63a0f5dd49a6.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T21:04:27Z"
      message: 'load-balancer-api-external: tcp connection to add0864408f98408387cb0980557d9ef-4b5d63a0f5dd49a6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.634262ms
      message: 'load-balancer-api-external: tcp connection to add0864408f98408387cb0980557d9ef-4b5d63a0f5dd49a6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:04:27Z"
    - latency: 8.141119ms
      message: 'load-balancer-api-external: resolved host name add0864408f98408387cb0980557d9ef-4b5d63a0f5dd49a6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:04:27Z"
    - latency: 3.638693ms
      message: 'load-balancer-api-external: tcp connection to add0864408f98408387cb0980557d9ef-4b5d63a0f5dd49a6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:03:27Z"
    - latency: 8.913073ms
      message: 'load-balancer-api-external: resolved host name add0864408f98408387cb0980557d9ef-4b5d63a0f5dd49a6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:03:27Z"
    - latency: 6.499314ms
      message: 'load-balancer-api-external: tcp connection to add0864408f98408387cb0980557d9ef-4b5d63a0f5dd49a6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:02:27Z"
    - latency: 8.084333ms
      message: 'load-balancer-api-external: resolved host name add0864408f98408387cb0980557d9ef-4b5d63a0f5dd49a6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:02:27Z"
    - latency: 4.493295ms
      message: 'load-balancer-api-external: tcp connection to add0864408f98408387cb0980557d9ef-4b5d63a0f5dd49a6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:01:27Z"
    - latency: 7.734918ms
      message: 'load-balancer-api-external: resolved host name add0864408f98408387cb0980557d9ef-4b5d63a0f5dd49a6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:01:27Z"
    - latency: 6.042705ms
      message: 'load-balancer-api-external: tcp connection to add0864408f98408387cb0980557d9ef-4b5d63a0f5dd49a6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:00:27Z"
    - latency: 6.884855ms
      message: 'load-balancer-api-external: resolved host name add0864408f98408387cb0980557d9ef-4b5d63a0f5dd49a6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:00:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T20:58:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-5-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-5.ec2.internal
      uid: 3279ca2d-3a78-45f0-b294-6f799c74504c
    resourceVersion: "22831"
    uid: de854bf2-87e1-45ee-812e-ee25e79124aa
  spec:
    sourcePod: network-check-source-685456655f-bhbhz
    targetEndpoint: add0864408f98408387cb0980557d9ef-4b5d63a0f5dd49a6.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T21:04:27Z"
      message: 'load-balancer-api-internal: tcp connection to add0864408f98408387cb0980557d9ef-4b5d63a0f5dd49a6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.609893ms
      message: 'load-balancer-api-internal: tcp connection to add0864408f98408387cb0980557d9ef-4b5d63a0f5dd49a6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:04:27Z"
    - latency: 8.104313ms
      message: 'load-balancer-api-internal: resolved host name add0864408f98408387cb0980557d9ef-4b5d63a0f5dd49a6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:04:27Z"
    - latency: 3.642481ms
      message: 'load-balancer-api-internal: tcp connection to add0864408f98408387cb0980557d9ef-4b5d63a0f5dd49a6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:03:27Z"
    - latency: 8.853757ms
      message: 'load-balancer-api-internal: resolved host name add0864408f98408387cb0980557d9ef-4b5d63a0f5dd49a6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:03:27Z"
    - latency: 6.588136ms
      message: 'load-balancer-api-internal: tcp connection to add0864408f98408387cb0980557d9ef-4b5d63a0f5dd49a6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:02:27Z"
    - latency: 8.11851ms
      message: 'load-balancer-api-internal: resolved host name add0864408f98408387cb0980557d9ef-4b5d63a0f5dd49a6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:02:27Z"
    - latency: 4.476516ms
      message: 'load-balancer-api-internal: tcp connection to add0864408f98408387cb0980557d9ef-4b5d63a0f5dd49a6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:01:27Z"
    - latency: 7.680285ms
      message: 'load-balancer-api-internal: resolved host name add0864408f98408387cb0980557d9ef-4b5d63a0f5dd49a6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:01:27Z"
    - latency: 6.416172ms
      message: 'load-balancer-api-internal: tcp connection to add0864408f98408387cb0980557d9ef-4b5d63a0f5dd49a6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:00:27Z"
    - latency: 6.943448ms
      message: 'load-balancer-api-internal: resolved host name add0864408f98408387cb0980557d9ef-4b5d63a0f5dd49a6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:00:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T20:58:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-5-to-network-check-target-ip-10-0-133-5
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-5.ec2.internal
      uid: 3279ca2d-3a78-45f0-b294-6f799c74504c
    resourceVersion: "24021"
    uid: bb3e8c1a-6d57-47d8-a3ac-20ea001d168c
  spec:
    sourcePod: network-check-source-685456655f-bhbhz
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T21:05:27Z"
      message: 'network-check-target-ip-10-0-133-5: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.204951ms
      message: 'network-check-target-ip-10-0-133-5: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:05:27Z"
    - latency: 876.58µs
      message: 'network-check-target-ip-10-0-133-5: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:04:27Z"
    - latency: 938.605µs
      message: 'network-check-target-ip-10-0-133-5: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:03:27Z"
    - latency: 1.176332ms
      message: 'network-check-target-ip-10-0-133-5: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:02:27Z"
    - latency: 869.545µs
      message: 'network-check-target-ip-10-0-133-5: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:01:27Z"
    - latency: 784.563µs
      message: 'network-check-target-ip-10-0-133-5: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:00:27Z"
    - latency: 1.620629ms
      message: 'network-check-target-ip-10-0-133-5: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:59:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T20:58:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-5-to-network-check-target-ip-10-0-137-19
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-5.ec2.internal
      uid: 3279ca2d-3a78-45f0-b294-6f799c74504c
    resourceVersion: "24022"
    uid: 84a0571c-7761-40ee-86aa-62434d4b7f5b
  spec:
    sourcePod: network-check-source-685456655f-bhbhz
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T21:05:27Z"
      message: 'network-check-target-ip-10-0-137-19: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.634316ms
      message: 'network-check-target-ip-10-0-137-19: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:05:27Z"
    - latency: 2.189034ms
      message: 'network-check-target-ip-10-0-137-19: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:04:27Z"
    - latency: 1.864811ms
      message: 'network-check-target-ip-10-0-137-19: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:03:27Z"
    - latency: 2.150414ms
      message: 'network-check-target-ip-10-0-137-19: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:02:27Z"
    - latency: 1.667822ms
      message: 'network-check-target-ip-10-0-137-19: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:01:27Z"
    - latency: 2.480528ms
      message: 'network-check-target-ip-10-0-137-19: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:00:27Z"
    - latency: 1.781917ms
      message: 'network-check-target-ip-10-0-137-19: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:59:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T20:58:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-5-to-network-check-target-ip-10-0-139-83
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-5.ec2.internal
      uid: 3279ca2d-3a78-45f0-b294-6f799c74504c
    resourceVersion: "24023"
    uid: 2255277e-891d-4aa4-84dd-8b7e1c207e79
  spec:
    sourcePod: network-check-source-685456655f-bhbhz
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T21:05:27Z"
      message: 'network-check-target-ip-10-0-139-83: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.172642ms
      message: 'network-check-target-ip-10-0-139-83: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:05:27Z"
    - latency: 2.327032ms
      message: 'network-check-target-ip-10-0-139-83: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:04:27Z"
    - latency: 2.273035ms
      message: 'network-check-target-ip-10-0-139-83: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:03:27Z"
    - latency: 2.21321ms
      message: 'network-check-target-ip-10-0-139-83: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:02:27Z"
    - latency: 1.95156ms
      message: 'network-check-target-ip-10-0-139-83: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:01:27Z"
    - latency: 2.51103ms
      message: 'network-check-target-ip-10-0-139-83: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:00:27Z"
    - latency: 2.353019ms
      message: 'network-check-target-ip-10-0-139-83: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:59:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T20:58:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-5-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-5.ec2.internal
      uid: 3279ca2d-3a78-45f0-b294-6f799c74504c
    resourceVersion: "22830"
    uid: dd6bdf07-7419-452f-ae3e-eac855c2f495
  spec:
    sourcePod: network-check-source-685456655f-bhbhz
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T21:04:27Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 880.315µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:04:27Z"
    - latency: 1.72195ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:04:27Z"
    - latency: 968.949µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:03:27Z"
    - latency: 1.881958ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:03:27Z"
    - latency: 1.490649ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:02:27Z"
    - latency: 1.602585ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:02:27Z"
    - latency: 774.993µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:01:27Z"
    - latency: 1.622292ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:01:27Z"
    - latency: 973.285µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:00:27Z"
    - latency: 1.723979ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:00:27Z"
kind: List
metadata:
  resourceVersion: ""