implement ScenarioOperation CRUD logic

[YamasouA]

What type of PR is this?

/area scenario
/kind feature

What this PR does / why we need it:

We implement scenario controller and the webhook.
And this controller and webhook are build as container.
We also implement scenario_operation controller logic.

Which issue(s) this PR fixes:

Part of #396

Special notes for your reviewer:

/label tide/merge-method-squash

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: YamasouA
Once this PR has been reviewed and has the lgtm label, please assign 196ikuchil for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[k8s-ci-robot]

Hi @YamasouA. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[YamasouA]

❯ cat valid-scenario.yaml
apiVersion: simulation.kube-scheduler-simulator.x-k8s.io/v1alpha1
kind: Scenario
metadata:
  name: valid-scenario
spec:
  foo: "valid test scenario"
  operations:
    - id: "op1"
      step: 1
      createOperation:
        object:
          apiVersion: v1
          kind: ConfigMap
          metadata:
            name: valid-configmap
          data:
            key: "value"

❯ kubectl apply -f valid-scenario.yaml
scenario.simulation.kube-scheduler-simulator.x-k8s.io/valid-scenario unchanged

❯ cat invalid-scenario.yaml
apiVersion: simulation.kube-scheduler-simulator.x-k8s.io/v1alpha1
kind: Scenario
metadata:
  name: invalid-scenario
spec:
  foo: "invalid test scenario"
  operations:
    - id: "op1"
      step: 1
      createOperation:
        object:
          apiVersion: v1
          kind: ConfigMap
          metadata:
            name: invalid-configmap
          data:
            key: "value"
      patchOperation:
        typeMeta:
          apiVersion: v1
          kind: ConfigMap
        objectMeta:
          name: invalid-configmap
        patch: '{"data":{"key":"new-value"}}'
        patchType: "StrategicMergePatch"

❯ kubectl apply -f invalid-scenario.yaml
Error from server (Forbidden): error when creating "invalid-scenario.yaml": admission webhook "vscenario-v1alpha1.kb.io" denied the request: scenario webhook ValidateCreate: validateOperation find some operations

[sanposhiho]

/ok-to-test
/cc @ordovicia @utam0k @saza-ku

[k8s-ci-robot]

@sanposhiho: GitHub didn't allow me to request PR reviews from the following users: ordovicia, saza-ku.

Note that only kubernetes-sigs members and repo collaborators can review this PR, and authors cannot review their own PRs.

In response to this:

/ok-to-test
/cc @ordovicia @utam0k @saza-ku

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[utam0k]

Overall, it looks good!

[utam0k]

nit

Suggested change

	return fmt.Errorf("validateOperation find some operations")
	return fmt.Errorf("exactly one operation type must be specified, but found %d", count)

[utam0k]

I think we should at least add the unit tests for this file.

[YamasouA]

@utam0k
Thank you for your review.
I add unit test!

[YamasouA]

/retest