Revert "Defining default path spec in ingress if hosts.*.paths is null"

[mustafaStakater]

This reverts PR #240.

[github-actions]

@mustafaStakater validation successful`

[d3adb5]

I personally don't see the problem with allowing use of a simpler interface for this kind of thing, though I wonder how often it would be used and whether its use should even be recommended over reproducing the classic Ingress path structure.

Nevertheless, I'm approving this one for now, but would also like to hear @rasheedamir's and @aslafy-z's opinions.

[mustafaStakater]

hmmmm, It creates redundancy in a sense that we can already define the same configuration via paths value.

I will be removing the else block so that users are forced to define basic paths value to avoid ambiguity. @d3adb5

[aslafy-z]

@mustafaStakater @d3adb5 I'd prefer to keep it simple and only expose the standard ingress path format as values. I think we can drop servicePort and serviceName too. However, if we go that way, it becomes a breaking change, thus, we'll have to bump the major.

[mustafaStakater]

We might have usecase for specifying multiple paths. @aslafy-z

[aslafy-z]

By "expose the standard ingress path format as values" I meant expose the whole paths list in the values as done in this revert. Ok to me.

[d3adb5]

I feel like this could break someone's existing setup, if they're reliant on the path fallback. It's not exactly warranting of a major bump, but caution is always good.

[rasheedamir]

@mustafaStakater what do you think? should we do major bump?

[mustafaStakater]

minor bump looks ok to me, a major bump seems too much

[mustafaStakater]

we can merge this