apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T17:37:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-94-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-94.ec2.internal
      uid: 17f99b13-4775-41f8-8404-53660e268a7a
    resourceVersion: "22541"
    uid: 0892c33b-a592-48f2-885c-431b6204da89
  spec:
    sourcePod: network-check-source-7d88cb55d8-766cw
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T17:44:46Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.090243ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:44:46Z"
    - latency: 1.196575ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:43:46Z"
    - latency: 993.527µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:42:46Z"
    - latency: 900.37µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:41:46Z"
    - latency: 1.079073ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:40:46Z"
    - latency: 1.015596ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:39:46Z"
    - latency: 1.081363ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:38:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T17:37:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-94-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-94.ec2.internal
      uid: 17f99b13-4775-41f8-8404-53660e268a7a
    resourceVersion: "21375"
    uid: 03f41b50-bfa6-4eeb-bb1d-3595ae0cf8bd
  spec:
    sourcePod: network-check-source-7d88cb55d8-766cw
    targetEndpoint: a630707aad8ba4d139b84a1f421dfd2a-514107a7564ea241.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T17:43:46Z"
      message: 'load-balancer-api-external: tcp connection to a630707aad8ba4d139b84a1f421dfd2a-514107a7564ea241.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.832876ms
      message: 'load-balancer-api-external: tcp connection to a630707aad8ba4d139b84a1f421dfd2a-514107a7564ea241.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:43:46Z"
    - latency: 8.672756ms
      message: 'load-balancer-api-external: resolved host name a630707aad8ba4d139b84a1f421dfd2a-514107a7564ea241.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T17:43:46Z"
    - latency: 4.3892ms
      message: 'load-balancer-api-external: tcp connection to a630707aad8ba4d139b84a1f421dfd2a-514107a7564ea241.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:42:46Z"
    - latency: 8.916091ms
      message: 'load-balancer-api-external: resolved host name a630707aad8ba4d139b84a1f421dfd2a-514107a7564ea241.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T17:42:46Z"
    - latency: 4.184847ms
      message: 'load-balancer-api-external: tcp connection to a630707aad8ba4d139b84a1f421dfd2a-514107a7564ea241.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:41:46Z"
    - latency: 8.58758ms
      message: 'load-balancer-api-external: resolved host name a630707aad8ba4d139b84a1f421dfd2a-514107a7564ea241.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T17:41:46Z"
    - latency: 4.554093ms
      message: 'load-balancer-api-external: tcp connection to a630707aad8ba4d139b84a1f421dfd2a-514107a7564ea241.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:40:46Z"
    - latency: 8.755722ms
      message: 'load-balancer-api-external: resolved host name a630707aad8ba4d139b84a1f421dfd2a-514107a7564ea241.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T17:40:46Z"
    - latency: 4.166496ms
      message: 'load-balancer-api-external: tcp connection to a630707aad8ba4d139b84a1f421dfd2a-514107a7564ea241.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:39:46Z"
    - latency: 7.921921ms
      message: 'load-balancer-api-external: resolved host name a630707aad8ba4d139b84a1f421dfd2a-514107a7564ea241.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T17:39:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T17:37:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-94-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-94.ec2.internal
      uid: 17f99b13-4775-41f8-8404-53660e268a7a
    resourceVersion: "21376"
    uid: 6040e3ad-d3a6-4349-ad4f-43e523e58e8c
  spec:
    sourcePod: network-check-source-7d88cb55d8-766cw
    targetEndpoint: a630707aad8ba4d139b84a1f421dfd2a-514107a7564ea241.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T17:43:46Z"
      message: 'load-balancer-api-internal: tcp connection to a630707aad8ba4d139b84a1f421dfd2a-514107a7564ea241.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.474765ms
      message: 'load-balancer-api-internal: tcp connection to a630707aad8ba4d139b84a1f421dfd2a-514107a7564ea241.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:43:46Z"
    - latency: 8.742889ms
      message: 'load-balancer-api-internal: resolved host name a630707aad8ba4d139b84a1f421dfd2a-514107a7564ea241.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T17:43:46Z"
    - latency: 4.447591ms
      message: 'load-balancer-api-internal: tcp connection to a630707aad8ba4d139b84a1f421dfd2a-514107a7564ea241.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:42:46Z"
    - latency: 8.935276ms
      message: 'load-balancer-api-internal: resolved host name a630707aad8ba4d139b84a1f421dfd2a-514107a7564ea241.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T17:42:46Z"
    - latency: 4.193937ms
      message: 'load-balancer-api-internal: tcp connection to a630707aad8ba4d139b84a1f421dfd2a-514107a7564ea241.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:41:46Z"
    - latency: 8.654527ms
      message: 'load-balancer-api-internal: resolved host name a630707aad8ba4d139b84a1f421dfd2a-514107a7564ea241.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T17:41:46Z"
    - latency: 4.446521ms
      message: 'load-balancer-api-internal: tcp connection to a630707aad8ba4d139b84a1f421dfd2a-514107a7564ea241.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:40:46Z"
    - latency: 8.859608ms
      message: 'load-balancer-api-internal: resolved host name a630707aad8ba4d139b84a1f421dfd2a-514107a7564ea241.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T17:40:46Z"
    - latency: 4.510986ms
      message: 'load-balancer-api-internal: tcp connection to a630707aad8ba4d139b84a1f421dfd2a-514107a7564ea241.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:39:46Z"
    - latency: 7.857467ms
      message: 'load-balancer-api-internal: resolved host name a630707aad8ba4d139b84a1f421dfd2a-514107a7564ea241.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T17:39:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T17:37:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-94-to-network-check-target-ip-10-0-130-104
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-94.ec2.internal
      uid: 17f99b13-4775-41f8-8404-53660e268a7a
    resourceVersion: "22539"
    uid: 14b00988-9e32-4dd8-a4a9-cee6340f1851
  spec:
    sourcePod: network-check-source-7d88cb55d8-766cw
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T17:44:46Z"
      message: 'network-check-target-ip-10-0-130-104: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.858498ms
      message: 'network-check-target-ip-10-0-130-104: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:44:46Z"
    - latency: 1.71442ms
      message: 'network-check-target-ip-10-0-130-104: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:43:46Z"
    - latency: 1.896186ms
      message: 'network-check-target-ip-10-0-130-104: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:42:46Z"
    - latency: 1.964305ms
      message: 'network-check-target-ip-10-0-130-104: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:41:46Z"
    - latency: 1.918992ms
      message: 'network-check-target-ip-10-0-130-104: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:40:46Z"
    - latency: 1.759627ms
      message: 'network-check-target-ip-10-0-130-104: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:39:46Z"
    - latency: 2.217734ms
      message: 'network-check-target-ip-10-0-130-104: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:38:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T17:37:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-94-to-network-check-target-ip-10-0-131-247
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-94.ec2.internal
      uid: 17f99b13-4775-41f8-8404-53660e268a7a
    resourceVersion: "22538"
    uid: c32b068b-f474-46c0-867b-fbc5dcc5efed
  spec:
    sourcePod: network-check-source-7d88cb55d8-766cw
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T17:44:46Z"
      message: 'network-check-target-ip-10-0-131-247: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.284054ms
      message: 'network-check-target-ip-10-0-131-247: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:44:46Z"
    - latency: 2.268793ms
      message: 'network-check-target-ip-10-0-131-247: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:43:46Z"
    - latency: 2.263931ms
      message: 'network-check-target-ip-10-0-131-247: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:42:46Z"
    - latency: 2.097351ms
      message: 'network-check-target-ip-10-0-131-247: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:41:46Z"
    - latency: 2.23228ms
      message: 'network-check-target-ip-10-0-131-247: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:40:46Z"
    - latency: 2.29535ms
      message: 'network-check-target-ip-10-0-131-247: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:39:46Z"
    - latency: 2.430687ms
      message: 'network-check-target-ip-10-0-131-247: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:38:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T17:37:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-94-to-network-check-target-ip-10-0-133-94
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-94.ec2.internal
      uid: 17f99b13-4775-41f8-8404-53660e268a7a
    resourceVersion: "22540"
    uid: b9eb3096-4825-4103-bc28-5200b65103da
  spec:
    sourcePod: network-check-source-7d88cb55d8-766cw
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T17:44:46Z"
      message: 'network-check-target-ip-10-0-133-94: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.501193ms
      message: 'network-check-target-ip-10-0-133-94: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:44:46Z"
    - latency: 943.642µs
      message: 'network-check-target-ip-10-0-133-94: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:43:46Z"
    - latency: 922.502µs
      message: 'network-check-target-ip-10-0-133-94: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:42:46Z"
    - latency: 1.117074ms
      message: 'network-check-target-ip-10-0-133-94: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:41:46Z"
    - latency: 886.616µs
      message: 'network-check-target-ip-10-0-133-94: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:40:46Z"
    - latency: 701.566µs
      message: 'network-check-target-ip-10-0-133-94: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:39:46Z"
    - latency: 1.33704ms
      message: 'network-check-target-ip-10-0-133-94: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:38:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T17:37:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-94-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-94.ec2.internal
      uid: 17f99b13-4775-41f8-8404-53660e268a7a
    resourceVersion: "21374"
    uid: bd8161dc-67be-4d1d-aad0-39f1ea71fa41
  spec:
    sourcePod: network-check-source-7d88cb55d8-766cw
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T17:43:46Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.185897ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:43:46Z"
    - latency: 1.905714ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T17:43:46Z"
    - latency: 918.688µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:42:46Z"
    - latency: 1.919683ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T17:42:46Z"
    - latency: 1.221499ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:41:46Z"
    - latency: 1.805329ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T17:41:46Z"
    - latency: 1.236589ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:40:46Z"
    - latency: 1.870301ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T17:40:46Z"
    - latency: 869.615µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:39:46Z"
    - latency: 1.69664ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T17:39:46Z"
kind: List
metadata:
  resourceVersion: ""