Nauticus icon indicating copy to clipboard operation
Nauticus copied to clipboard

Bug Report: Nauticus Controller Fails to Update Space on Resource Quota Override Edit

Open smileisak opened this issue 1 year ago • 3 comments

Bug description

Issue: When creating a space from a template with resource quota override, the initial creation works as expected. However, subsequent edits to the space, specifically updating the overridden resource quota values, do not prompt any reaction or update from the nauticus-controller.

How to reproduce

Steps to reproduce the behavior:

  1. Set Up a Kind Cluster: Initialize a new kind cluster for testing.
  2. Apply the Space Template: Use the space template provided in config/samples to set up the initial space.
  3. Apply the Space Override: Implement a resource quota override on the created space.
  4. Edit the Space: Use kubectl edit to modify the space, particularly changing a resource quota value.

Expected behavior

The expected behavior is that the nauticus-controller should detect changes made to the space's resource quota and update accordingly. This should include applying the new quota values to the space.

Logs

If applicable, please provide logs of nauticus-controller.

Nothing happens, so there is no logs.

Additional context

Nauticus version: v0.2.0 Helm Chart version: v0.2.0 Kubernetes version: v1.27.2

smileisak avatar Nov 19 '23 15:11 smileisak

This is stale, but we won't close it automatically, just bare in mind the maintainers may be busy with other tasks and will reach your issue ASAP. If you have any question or request to prioritize this, please reach #nauticus on Kubernetes Slack.

github-actions[bot] avatar Dec 20 '23 01:12 github-actions[bot]

After thoroughly reviewing the steps you've outlined and attempting to reproduce the issue within the specified environment, I've found that the controller behaves as expected, responding appropriately to the resource quota modifications.

abelhoula avatar Feb 06 '24 20:02 abelhoula

This is stale, but we won't close it automatically, just bare in mind the maintainers may be busy with other tasks and will reach your issue ASAP. If you have any question or request to prioritize this, please reach #nauticus on Kubernetes Slack.

github-actions[bot] avatar Mar 08 '24 02:03 github-actions[bot]