import org.lastaflute.web.validation.theme.conversion.ValidateTypeFailure;

import jakarta.validation.constraints.Size;

/**
 * Form class for editing web crawling configurations in the admin interface.
 * This form extends CreateForm to include fields necessary for updating existing web config entries,
 * including tracking information for optimistic locking and audit trails.

import org.lastaflute.web.validation.theme.conversion.ValidateTypeFailure;

import jakarta.validation.constraints.Size;

/**
 * Form class for editing file crawling configurations in the admin interface.
 * This form extends CreateForm to include fields necessary for updating existing file config entries,
 * including tracking information for optimistic locking and audit trails.

import org.lastaflute.web.validation.theme.conversion.ValidateTypeFailure;

import jakarta.validation.constraints.Size;

/**
 * Form class for editing key match configurations in the admin interface.
 * This form extends CreateForm to include fields necessary for updating existing key match entries,
 * including tracking information for optimistic locking and audit trails.

            op.setup(form -> {
                form.initialize();
                form.crudMode = CrudMode.CREATE;
            });
        });
    }

    /**
     * Displays the form for editing an existing duplicate host configuration.
     *
     * @param form the edit form containing the duplicate host ID
     * @return HTML response for the duplicate host edit form
     */
    @Execute
    @Secured({ ROLE })

```

### Existing object replication

Existing object replication as detailed [here](https://aws.amazon.com/blogs/storage/replicating-existing-objects-between-s3-buckets/) can be enabled by passing `existing-objects` as a value to `--replicate` flag while adding or editing a replication rule.

the vast majority of deployments in any negative way.

> Will an upgrade of an existing MinIO cluster impact the SLA of the cluster or will it even cause downtime?

No, an upgrade should not cause any downtime. However, on the first startup -
since MinIO will attempt to migrate any existing IAM data - the boot process may
take slightly longer, but may not be visibly noticeable. Once the migration has

            return null;
        });

        return asJson(new ApiUpdateResponse().id(relatedQuery.getId()).created(true).status(Status.OK).result());
    }

    /**
     * Updates an existing related query setting.
     *
     * @param body the related query configuration data to update
     * @return JSON response containing the updated related query ID and status
     */

            op.setup(form -> {
                form.initialize();
                form.crudMode = CrudMode.CREATE;
            });
        });
    }

    /**
     * Displays the form for editing an existing related content item.
     *
     * @param form the edit form containing the ID of the item to edit
     * @return HTML response for the edit form
     */
    @Execute
    @Secured({ ROLE })

            op.setup(form -> {
                form.initialize();
                form.crudMode = CrudMode.CREATE;
            });
        });
    }

    /**
     * Displays the form for editing an existing path mapping.
     *
     * @param form the edit form containing the path mapping ID and data
     * @return HTML response for the path mapping edit form
     */
    @Execute
    @Secured({ ROLE })

EndpointSlices with Pod referencing Nodes that don't exist couldn't be created or updated. The behavior on the EndpointSlice controller has been modified to update the EndpointSlice without the Pods that reference non-existing Nodes and keep retrying until all Pods reference existing Nodes. However, if `service.Spec.PublishNotReadyAddresses` is set, all the Pods are published without retrying. Fixed EndpointSlices metrics to reflect correctly the number of desired EndpointSlices when no endpoints...