Memcached Still Present When Set To False In Values #11

New Issue

2020-08-25T19:27:58Z

sstubbs commented

2020-08-25 19:27:58 +00:00

(Migrated from gitea.com)

Hi,

The memcached deployment is still being added when:

  cache:
    builtIn:
      enabled: false

Hi, The memcached deployment is still being added when: ``` cache: builtIn: enabled: false ```

luhahn commented

2020-08-26 06:40:57 +00:00

(Migrated from gitea.com)

Yep, I just saw that the condition check is wrong on memcache. Thanks for finding that. Since I missed the builtIn part in the condition check you can use:

gitea:
 cache:
  enabled: false

That should work until I've patched that.

Yep, I just saw that the condition check is wrong on memcache. Thanks for finding that. Since I missed the builtIn part in the condition check you can use: ```yaml gitea: cache: enabled: false ``` That should work until I've patched that.

sstubbs commented

2020-08-28 19:40:07 +00:00

(Migrated from gitea.com)

This works thanks

sstubbs commented

2020-08-30 20:14:42 +00:00

(Migrated from gitea.com)

I've noticed that if I do this the memcached doesn't run like I want but the gitea config still has it there. I've manually changed the condition in the Chart.yaml to condition: gitea.cache.builtIn.enabled and it seems to work now.

I've noticed that if I do this the memcached doesn't run like I want but the gitea config still has it there. I've manually changed the condition in the Chart.yaml to `condition: gitea.cache.builtIn.enabled` and it seems to work now.

sstubbs commented

2020-08-30 20:23:51 +00:00

(Migrated from gitea.com)

Can this be fixed in the chart?

luhahn commented

2020-08-31 06:49:13 +00:00

(Migrated from gitea.com)

Sure, I'll prepare a pull request with a few fixes

sstubbs commented

2020-09-01 01:05:22 +00:00

(Migrated from gitea.com)

Great thank you.