fix: chart path can't be relative

[knelasevero]

For context:

• I created a PR to check if the CI would fail with a broken template:
  Triggering chart CI to see if it fails #870

• It didn't:
  https://github.com/kubernetes-sigs/descheduler/pull/870/checks

• Turns out the culprit was just the ./charts path at the config file in .github/ci/ct.yaml, so it was ignoring and not checking the chart

There are a few other things worth discussing here:

• Chart testing is complaining about using 'Kubernetes SIG Scheduling' as the maintainer of the chart. It expects a valid github/gitlab/something user. @damemi @ingvagabund Who should I put there? I can also put my name there if you folks think it is appropriate, now that I am making changes here.

• I still need to add chart-testing installation checking. Will do that after linting is green.

[k8s-ci-robot]

Hi @knelasevero. 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/test-infra repository.

[damemi]

/ok-to-test

[damemi]

Thanks for the work @knelasevero

Chart testing is complaining about using 'Kubernetes SIG Scheduling' as the maintainer of the chart. It expects a valid github/gitlab/something user.

That's annoying. It would really be ideal if we can keep the SIG list as the maintainer to reduce the number of places we need to coordinate admins. Is there any way we can skip this check?

[knelasevero]

That's annoying. It would really be ideal if we can keep the SIG list as the maintainer to reduce the number of places we need to coordinate admins. Is there any way we can skip this check?

It seems --validate-maintainers=false did the trick :)

[a7i]

/lgtm

[damemi]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: damemi

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [damemi]

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