apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T18:20:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-53-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-53.ec2.internal
      uid: 17e76f2b-46a7-43b6-8c9b-650851bfcda5
    resourceVersion: "22229"
    uid: 8d4f578c-5dae-456f-b06e-ad6d56c7642c
  spec:
    sourcePod: network-check-source-869dcfcdcd-s5fhg
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T18:27:10Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 839.577µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T18:27:10Z"
    - latency: 1.096209ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T18:26:10Z"
    - latency: 1.273585ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T18:25:10Z"
    - latency: 881.185µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T18:24:10Z"
    - latency: 1.371995ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T18:23:10Z"
    - latency: 955.206µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T18:22:10Z"
    - latency: 1.190535ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T18:21:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T18:20:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-53-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-53.ec2.internal
      uid: 17e76f2b-46a7-43b6-8c9b-650851bfcda5
    resourceVersion: "21021"
    uid: 6bb3b72a-59a9-45f4-9c2a-8d8545ca545a
  spec:
    sourcePod: network-check-source-869dcfcdcd-s5fhg
    targetEndpoint: a4c74e079641e4991bd8095bcb12466e-781295fa099d2e9c.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T18:26:10Z"
      message: 'load-balancer-api-external: tcp connection to a4c74e079641e4991bd8095bcb12466e-781295fa099d2e9c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.743292ms
      message: 'load-balancer-api-external: tcp connection to a4c74e079641e4991bd8095bcb12466e-781295fa099d2e9c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T18:26:10Z"
    - latency: 8.277234ms
      message: 'load-balancer-api-external: resolved host name a4c74e079641e4991bd8095bcb12466e-781295fa099d2e9c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T18:26:10Z"
    - latency: 4.563057ms
      message: 'load-balancer-api-external: tcp connection to a4c74e079641e4991bd8095bcb12466e-781295fa099d2e9c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T18:25:10Z"
    - latency: 7.140338ms
      message: 'load-balancer-api-external: resolved host name a4c74e079641e4991bd8095bcb12466e-781295fa099d2e9c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T18:25:10Z"
    - latency: 4.882842ms
      message: 'load-balancer-api-external: tcp connection to a4c74e079641e4991bd8095bcb12466e-781295fa099d2e9c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T18:24:10Z"
    - latency: 7.997927ms
      message: 'load-balancer-api-external: resolved host name a4c74e079641e4991bd8095bcb12466e-781295fa099d2e9c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T18:24:10Z"
    - latency: 4.627433ms
      message: 'load-balancer-api-external: tcp connection to a4c74e079641e4991bd8095bcb12466e-781295fa099d2e9c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T18:23:10Z"
    - latency: 6.92015ms
      message: 'load-balancer-api-external: resolved host name a4c74e079641e4991bd8095bcb12466e-781295fa099d2e9c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T18:23:10Z"
    - latency: 4.931259ms
      message: 'load-balancer-api-external: tcp connection to a4c74e079641e4991bd8095bcb12466e-781295fa099d2e9c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T18:22:10Z"
    - latency: 6.663735ms
      message: 'load-balancer-api-external: resolved host name a4c74e079641e4991bd8095bcb12466e-781295fa099d2e9c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T18:22:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T18:20:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-53-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-53.ec2.internal
      uid: 17e76f2b-46a7-43b6-8c9b-650851bfcda5
    resourceVersion: "21022"
    uid: 14dbfbdc-7af8-4617-9f89-fe8d4e2ce474
  spec:
    sourcePod: network-check-source-869dcfcdcd-s5fhg
    targetEndpoint: a4c74e079641e4991bd8095bcb12466e-781295fa099d2e9c.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T18:26:10Z"
      message: 'load-balancer-api-internal: tcp connection to a4c74e079641e4991bd8095bcb12466e-781295fa099d2e9c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.605143ms
      message: 'load-balancer-api-internal: tcp connection to a4c74e079641e4991bd8095bcb12466e-781295fa099d2e9c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T18:26:10Z"
    - latency: 8.394886ms
      message: 'load-balancer-api-internal: resolved host name a4c74e079641e4991bd8095bcb12466e-781295fa099d2e9c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T18:26:10Z"
    - latency: 4.404466ms
      message: 'load-balancer-api-internal: tcp connection to a4c74e079641e4991bd8095bcb12466e-781295fa099d2e9c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T18:25:10Z"
    - latency: 7.120618ms
      message: 'load-balancer-api-internal: resolved host name a4c74e079641e4991bd8095bcb12466e-781295fa099d2e9c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T18:25:10Z"
    - latency: 5.255824ms
      message: 'load-balancer-api-internal: tcp connection to a4c74e079641e4991bd8095bcb12466e-781295fa099d2e9c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T18:24:10Z"
    - latency: 7.978547ms
      message: 'load-balancer-api-internal: resolved host name a4c74e079641e4991bd8095bcb12466e-781295fa099d2e9c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T18:24:10Z"
    - latency: 4.627091ms
      message: 'load-balancer-api-internal: tcp connection to a4c74e079641e4991bd8095bcb12466e-781295fa099d2e9c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T18:23:10Z"
    - latency: 6.873397ms
      message: 'load-balancer-api-internal: resolved host name a4c74e079641e4991bd8095bcb12466e-781295fa099d2e9c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T18:23:10Z"
    - latency: 4.83966ms
      message: 'load-balancer-api-internal: tcp connection to a4c74e079641e4991bd8095bcb12466e-781295fa099d2e9c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T18:22:10Z"
    - latency: 6.776754ms
      message: 'load-balancer-api-internal: resolved host name a4c74e079641e4991bd8095bcb12466e-781295fa099d2e9c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T18:22:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T18:20:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-53-to-network-check-target-ip-10-0-130-53
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-53.ec2.internal
      uid: 17e76f2b-46a7-43b6-8c9b-650851bfcda5
    resourceVersion: "22226"
    uid: 5af3d56c-a93e-4dca-8324-502e9c376fdc
  spec:
    sourcePod: network-check-source-869dcfcdcd-s5fhg
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T18:27:10Z"
      message: 'network-check-target-ip-10-0-130-53: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 892.171µs
      message: 'network-check-target-ip-10-0-130-53: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T18:27:10Z"
    - latency: 925.114µs
      message: 'network-check-target-ip-10-0-130-53: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T18:26:10Z"
    - latency: 957.612µs
      message: 'network-check-target-ip-10-0-130-53: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T18:25:10Z"
    - latency: 1.021662ms
      message: 'network-check-target-ip-10-0-130-53: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T18:24:10Z"
    - latency: 876.653µs
      message: 'network-check-target-ip-10-0-130-53: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T18:23:10Z"
    - latency: 1.435477ms
      message: 'network-check-target-ip-10-0-130-53: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T18:22:10Z"
    - latency: 1.604024ms
      message: 'network-check-target-ip-10-0-130-53: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T18:21:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T18:20:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-53-to-network-check-target-ip-10-0-133-129
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-53.ec2.internal
      uid: 17e76f2b-46a7-43b6-8c9b-650851bfcda5
    resourceVersion: "22227"
    uid: 8c7e3a0b-1e7b-4f2d-a9e1-61f0341c1b6b
  spec:
    sourcePod: network-check-source-869dcfcdcd-s5fhg
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T18:27:10Z"
      message: 'network-check-target-ip-10-0-133-129: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.571636ms
      message: 'network-check-target-ip-10-0-133-129: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T18:27:10Z"
    - latency: 2.322014ms
      message: 'network-check-target-ip-10-0-133-129: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T18:26:10Z"
    - latency: 2.387396ms
      message: 'network-check-target-ip-10-0-133-129: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T18:25:10Z"
    - latency: 2.54704ms
      message: 'network-check-target-ip-10-0-133-129: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T18:24:10Z"
    - latency: 2.169133ms
      message: 'network-check-target-ip-10-0-133-129: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T18:23:10Z"
    - latency: 2.714277ms
      message: 'network-check-target-ip-10-0-133-129: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T18:22:10Z"
    - latency: 2.700353ms
      message: 'network-check-target-ip-10-0-133-129: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T18:21:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T18:20:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-53-to-network-check-target-ip-10-0-136-255
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-53.ec2.internal
      uid: 17e76f2b-46a7-43b6-8c9b-650851bfcda5
    resourceVersion: "22228"
    uid: c8db5f90-1377-44ce-8d42-976e01a06f3f
  spec:
    sourcePod: network-check-source-869dcfcdcd-s5fhg
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T18:27:10Z"
      message: 'network-check-target-ip-10-0-136-255: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.62017ms
      message: 'network-check-target-ip-10-0-136-255: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T18:27:10Z"
    - latency: 2.404707ms
      message: 'network-check-target-ip-10-0-136-255: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T18:26:10Z"
    - latency: 2.318083ms
      message: 'network-check-target-ip-10-0-136-255: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T18:25:10Z"
    - latency: 2.19107ms
      message: 'network-check-target-ip-10-0-136-255: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T18:24:10Z"
    - latency: 2.421567ms
      message: 'network-check-target-ip-10-0-136-255: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T18:23:10Z"
    - latency: 2.365299ms
      message: 'network-check-target-ip-10-0-136-255: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T18:22:10Z"
    - latency: 2.478036ms
      message: 'network-check-target-ip-10-0-136-255: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T18:21:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T18:20:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-53-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-53.ec2.internal
      uid: 17e76f2b-46a7-43b6-8c9b-650851bfcda5
    resourceVersion: "21020"
    uid: 84fa1f80-8777-4832-8c00-651186dae0d5
  spec:
    sourcePod: network-check-source-869dcfcdcd-s5fhg
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T18:26:10Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 892.302µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T18:26:10Z"
    - latency: 1.791329ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T18:26:10Z"
    - latency: 1.012302ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T18:25:10Z"
    - latency: 1.785442ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T18:25:10Z"
    - latency: 877.419µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T18:24:10Z"
    - latency: 1.968761ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T18:24:10Z"
    - latency: 931.371µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T18:23:10Z"
    - latency: 1.520314ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T18:23:10Z"
    - latency: 1.202853ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T18:22:10Z"
    - latency: 1.94069ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T18:22:10Z"
kind: List
metadata:
  resourceVersion: ""