Fix typo in Dockerfile_k8s_dev

[pdostal]

No description provided.

[ricardobranco777]

LGTM

[asmorodskyi]

please don't merge PRs with failed tests , this should be hard rule

[asmorodskyi]

ok I created a rule for master branch which will disable such ability ....

[ricardobranco777]

please don't merge PRs with failed tests , this should be hard rule

In this case it was failing because the Selenium test was failing (reason: updated Selenium package).

I should have merged my PR fixing it first and told Pavel to rebase this one.

[ricardobranco777]

ok I created a rule for master branch which will disable such ability ....

What will happen in the case of codecov failing?

[asmorodskyi]

please don't merge PRs with failed tests , this should be hard rule

In this case it was failing because the Selenium test was failing (reason: updated Selenium package).

I should have merged my PR fixing it first and told Pavel to rebase this one.

yes I get that part that Pavel's PR does not introduce the problem , but from my POV it does not change anything . When tests are failing repo considered as "broken" and should be fixed before anything else will be merged into it

[asmorodskyi]

ok I created a rule for master branch which will disable such ability ....

What will happen in the case of codecov failing?

1. Make codecov not to fail , and this can be achieved in two ways :
   - relax failure conditions ( e.g. if test currently failing because we don't achieve coverage 75% than we set it to fail when we not achieve coverage 70% )
   - make it not to fail in "natural way" :)
2. Disable codecov pipeline full

All in all having something which is constantly failing and we ignore this it is bad practice and should be avoided as much as possible