robolaunch/fleet-operator

Issues

• Every Pod Controller Should Use `IfNotPresent` as Image Pull Policy

  #33 opened a year ago by tunahanertekin
  0

• Fleet Operator crashes when checking FederatedNamespace

  #31 opened a year ago by tunahanertekin
  0

• Support ROS 2 Domain Bridge

  #30 opened a year ago by tunahanertekin
  0

• Fleet Cannot be Informed When FederatedNamespace is Mutated

  #29 opened a year ago by tunahanertekin
  1

• ServiceExport does not export DiscoveryServer service

  #27 opened a year ago by tunahanertekin
  0

• Owned Federated Namespace is Not Being Updated When Changing `.spec.instances`

  #25 opened a year ago by tunahanertekin
  0

• Automate Helm Chart Creation w/ Helmify

  #23 opened a year ago by tunahanertekin
  0

• Generate API Reference Document

  #21 opened a year ago by tunahanertekin
  0

• Add Owned Object's References to Custom Resource APIs (robolaunch/robot-operator#100)

  #19 opened a year ago by tunahanertekin
  0

• Cover Cloud Powered Robot Deployment

  #3 opened 2 years ago by tunahanertekin
  0

• Shorten the Discovery Server Status Mirror

  #15 opened 2 years ago by tunahanertekin
  0

• Create Federated Namespace

  #16 opened 2 years ago by tunahanertekin
  0

• Update Tenancy Labels

  #13 opened 2 years ago by tunahanertekin
  0

• Enable Differentiating Robots by Cluster

  #12 opened 2 years ago by tunahanertekin
  0

• Manage Fleet Custom Resource

  #4 opened 2 years ago by tunahanertekin
  0

• Manage Multiple Robot Deployments

  #6 opened 2 years ago by tunahanertekin
  0

• Manage Discovery Server Configuration of Robots

  #7 opened 2 years ago by tunahanertekin
  0

• Manage Kubernetes Namespace with Fleet

  #5 opened 2 years ago by tunahanertekin
  0

• Manage Connectivity of N # of Robots

  #2 opened 2 years ago by tunahanertekin
  0

• Manage Lifecycle of Multiple Robots

  #1 opened 2 years ago by tunahanertekin
  0