apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T15:48:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-4-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-4.ec2.internal
      uid: d5432bb0-88d1-4fc9-a59b-815af47df5fc
    resourceVersion: "10887"
    uid: fd9c9f46-502f-4d3e-8e3c-4c205903ae68
  spec:
    sourcePod: network-check-source-7d88cb55d8-568cj
    targetEndpoint: 172.31.0.1:443
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T15:48:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-4-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-4.ec2.internal
      uid: d5432bb0-88d1-4fc9-a59b-815af47df5fc
    resourceVersion: "14345"
    uid: 794c0fda-4b5b-4591-828a-a29b2f322f9f
  spec:
    sourcePod: network-check-source-7d88cb55d8-568cj
    targetEndpoint: aa77a8c808be7447a8a976596ee42aac-130b378cb8215447.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T15:54:55Z"
      message: 'load-balancer-api-external: tcp connection to aa77a8c808be7447a8a976596ee42aac-130b378cb8215447.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.830238ms
      message: 'load-balancer-api-external: tcp connection to aa77a8c808be7447a8a976596ee42aac-130b378cb8215447.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:54:55Z"
    - latency: 8.308476ms
      message: 'load-balancer-api-external: resolved host name aa77a8c808be7447a8a976596ee42aac-130b378cb8215447.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T15:54:55Z"
    - latency: 4.881699ms
      message: 'load-balancer-api-external: tcp connection to aa77a8c808be7447a8a976596ee42aac-130b378cb8215447.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:53:55Z"
    - latency: 7.408161ms
      message: 'load-balancer-api-external: resolved host name aa77a8c808be7447a8a976596ee42aac-130b378cb8215447.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T15:53:55Z"
    - latency: 4.835011ms
      message: 'load-balancer-api-external: tcp connection to aa77a8c808be7447a8a976596ee42aac-130b378cb8215447.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:52:55Z"
    - latency: 6.731633ms
      message: 'load-balancer-api-external: resolved host name aa77a8c808be7447a8a976596ee42aac-130b378cb8215447.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T15:52:55Z"
    - latency: 6.054531ms
      message: 'load-balancer-api-external: tcp connection to aa77a8c808be7447a8a976596ee42aac-130b378cb8215447.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:51:55Z"
    - latency: 7.075048ms
      message: 'load-balancer-api-external: resolved host name aa77a8c808be7447a8a976596ee42aac-130b378cb8215447.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T15:51:55Z"
    - latency: 5.256025ms
      message: 'load-balancer-api-external: tcp connection to aa77a8c808be7447a8a976596ee42aac-130b378cb8215447.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:50:55Z"
    - latency: 6.63909ms
      message: 'load-balancer-api-external: resolved host name aa77a8c808be7447a8a976596ee42aac-130b378cb8215447.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T15:50:55Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T15:48:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-4-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-4.ec2.internal
      uid: d5432bb0-88d1-4fc9-a59b-815af47df5fc
    resourceVersion: "14346"
    uid: 3ebf29a2-da8d-42ca-b916-943f8ca055a4
  spec:
    sourcePod: network-check-source-7d88cb55d8-568cj
    targetEndpoint: aa77a8c808be7447a8a976596ee42aac-130b378cb8215447.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T15:54:55Z"
      message: 'load-balancer-api-internal: tcp connection to aa77a8c808be7447a8a976596ee42aac-130b378cb8215447.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.865953ms
      message: 'load-balancer-api-internal: tcp connection to aa77a8c808be7447a8a976596ee42aac-130b378cb8215447.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:54:55Z"
    - latency: 8.389257ms
      message: 'load-balancer-api-internal: resolved host name aa77a8c808be7447a8a976596ee42aac-130b378cb8215447.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T15:54:55Z"
    - latency: 5.156622ms
      message: 'load-balancer-api-internal: tcp connection to aa77a8c808be7447a8a976596ee42aac-130b378cb8215447.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:53:55Z"
    - latency: 7.516008ms
      message: 'load-balancer-api-internal: resolved host name aa77a8c808be7447a8a976596ee42aac-130b378cb8215447.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T15:53:55Z"
    - latency: 4.800895ms
      message: 'load-balancer-api-internal: tcp connection to aa77a8c808be7447a8a976596ee42aac-130b378cb8215447.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:52:55Z"
    - latency: 6.767975ms
      message: 'load-balancer-api-internal: resolved host name aa77a8c808be7447a8a976596ee42aac-130b378cb8215447.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T15:52:55Z"
    - latency: 10.058428ms
      message: 'load-balancer-api-internal: tcp connection to aa77a8c808be7447a8a976596ee42aac-130b378cb8215447.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:51:55Z"
    - latency: 7.104064ms
      message: 'load-balancer-api-internal: resolved host name aa77a8c808be7447a8a976596ee42aac-130b378cb8215447.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T15:51:55Z"
    - latency: 5.268944ms
      message: 'load-balancer-api-internal: tcp connection to aa77a8c808be7447a8a976596ee42aac-130b378cb8215447.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:50:55Z"
    - latency: 6.697207ms
      message: 'load-balancer-api-internal: resolved host name aa77a8c808be7447a8a976596ee42aac-130b378cb8215447.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T15:50:55Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T15:48:54Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-4-to-network-check-target-ip-10-0-136-4
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-4.ec2.internal
      uid: d5432bb0-88d1-4fc9-a59b-815af47df5fc
    resourceVersion: "10893"
    uid: dd8fa08a-fafc-46a4-993a-87611b991054
  spec:
    sourcePod: network-check-source-7d88cb55d8-568cj
    targetEndpoint: 10.132.0.4:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T15:48:54Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-4-to-network-check-target-ip-10-0-137-65
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-4.ec2.internal
      uid: d5432bb0-88d1-4fc9-a59b-815af47df5fc
    resourceVersion: "10896"
    uid: fad9684a-be01-49e4-98ff-7c5916bfbeac
  spec:
    sourcePod: network-check-source-7d88cb55d8-568cj
    targetEndpoint: 10.133.0.3:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T15:48:54Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-4-to-network-check-target-ip-10-0-142-124
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-4.ec2.internal
      uid: d5432bb0-88d1-4fc9-a59b-815af47df5fc
    resourceVersion: "10898"
    uid: 34e0481d-c23a-42bd-8d4f-cc196e55e36b
  spec:
    sourcePod: network-check-source-7d88cb55d8-568cj
    targetEndpoint: 10.134.0.3:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T15:48:54Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-4-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-4.ec2.internal
      uid: d5432bb0-88d1-4fc9-a59b-815af47df5fc
    resourceVersion: "14344"
    uid: e89b6740-4a0f-480c-9411-8b201b21f84d
  spec:
    sourcePod: network-check-source-7d88cb55d8-568cj
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T15:54:55Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 957.377µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:54:55Z"
    - latency: 1.653016ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T15:54:55Z"
    - latency: 891.399µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:53:55Z"
    - latency: 1.83094ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T15:53:55Z"
    - latency: 998.903µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:52:55Z"
    - latency: 1.802146ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T15:52:55Z"
    - latency: 856.129µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:51:55Z"
    - latency: 1.846826ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T15:51:55Z"
    - latency: 823.124µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:50:55Z"
    - latency: 1.634237ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T15:50:55Z"
kind: List
metadata:
  resourceVersion: ""